BIND 10 #1673: Decode exit status in boss

BIND 10 Development do-not-reply at isc.org
Tue Feb 14 08:32:19 UTC 2012


#1673: Decode exit status in boss
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Boss of BIND  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 The `BIND10_COMPONENT_FAILED component %1 (pid %2) failed with %3 exit
 status` log message is not too helpful (as can be seen in #1672, for
 example), as it produces the exit status in raw, undecoded format. We
 might want to use some of these functions to decode it and provide some
 reasonable output:
  * `os.WCOREDUMP()`
  * `os.WIFCONTINUED()`
  * `os.WIFSTOPPED()`
  * `os.WIFSIGNALED()`
  * `os.WIFEXITED()`
  * `os.WSTOPSIG()`

-- 
Ticket URL: <http://bind10.isc.org/ticket/1673>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list