BIND 10 #213: Change hard-coded process startups to configuration-driven
BIND 10 Development
do-not-reply at isc.org
Tue Oct 25 08:46:32 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 vorner):
Hello
Replying to [comment:21 jinmei]:
> > 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'
> }}}
Sorry, this is my fault. This is a code from yesterday afternoon, moving
away from os.kill, I didn't have time to try it then (and, as usual, this
is the part which handles external processes so it doesn't have a unittest
:-|). Should be fixed now.
--
Ticket URL: <http://bind10.isc.org/ticket/213#comment:22>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list