Opened 8 years ago

Closed 6 years ago

#1652 closed enhancement (wontfix)

msgq write to stderr on startup and exit status

Reported by: jreed Owned by:
Priority: low Milestone: Remaining BIND10 tickets
Component: ~msgq (obsolete) Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

If msgq has a failure when it attempts to start, it should write to stderr and also have return some exit status indicating the problem.

(As mentioned in F2F 2012-01.)

Subtickets

Change History (4)

comment:1 Changed 8 years ago by jreed

  • Type changed from defect to enhancement

comment:2 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.