BIND 10 #213: Change hard-coded process startups to configuration-driven
BIND 10 Development
do-not-reply at isc.org
Mon Oct 24 23:40:00 UTC 2011
#213: Change hard-coded process startups to configuration-driven
-------------------------------------+-------------------------------------
Reporter: shane | Owner: vorner
Type: | Status: reviewing
enhancement | Milestone:
Priority: major | Sprint-20111025
Component: Boss | Resolution:
of BIND | Sensitive: 0
Keywords: | Sub-Project: Core
Defect Severity: N/A | Estimated Difficulty: 9
Feature Depending on Ticket: | Total Hours:
Add Hours to Ticket: |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:19 vorner]:
> > - When I stopped the system via bindctl 'Boss shutdown', the bind10
> > process raised an exception:
[...]
> I couldn't reproduce this, it worked for me. But I added some handling
of this, so it shouldn't cause an exception any more (I expect this
happens in some time when the component is already stopped, but it didn't
yet get the SIGCHLD or something).
>
> Anyway, I find it strange it did bring the system down without killing
msgq. Or maybe not, considering where the exception happened.
It (after pulling the latest code) still fails, but now in a different
way. Maybe it's MacOS specific?
{{{
Traceback (most recent call last):
File "/Users/jinmei/opt/sbin/bind10", line 967, in <module>
main()
File "/Users/jinmei/opt/sbin/bind10", line 962, in main
boss_of_bind.shutdown()
File "/Users/jinmei/opt/sbin/bind10", line 655, in shutdown
component.kill()
File "/Users/jinmei/opt/lib/python3.1/site-
packages/isc/bind10/component.py", line 286, in kill
self._procinfo.terminate()
AttributeError: 'ProcessInfo' object has no attribute 'terminate'
}}}
and b10-msgq didn't die.
--
Ticket URL: <http://bind10.isc.org/ticket/213#comment:21>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list