BIND 10 #642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around
BIND 10 Development
do-not-reply at isc.org
Tue Apr 19 11:11:54 UTC 2011
#642: SIGHUP and other signals cause boss to leave BIND 10 processes lying around
-------------------------------------+-------------------------------------
Reporter: shane | Owner: shane
Type: defect | Status: reviewing
Priority: minor | Milestone:
Component: Boss of | Sprint-20110419
BIND | Resolution:
Keywords: | Sensitive: 0
Estimated Number of Hours: 0.0 | Add Hours to Ticket: 0
Billable?: 1 | Total Hours: 0
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => shane
Comment:
Hello
The code looks OK. But still, if I start it in a terminal with & and then
exit the terminal (this time, it was ssh connection), it still survives
and starts dying out one by one. Should I have a look what happens at my
side and why this is happening?
Thanks
--
Ticket URL: <http://bind10.isc.org/ticket/642#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list