[nsd-users] NSD as slave leaves a child process behind
matthijs at NLnetLabs.nl
Tue Oct 20 09:49:56 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
It could be that the shutdown signal was successfully send to the xfrd
process, but that it is quite busy at the moment.
I have done some testing with 10.000 zones of 7 RRs a zone. It sometimes
takes a couple of seconds before the xfrd process really terminated. But
eventually, the xfrd process should shut down. This might happen after
the nsdc stop command returned 0.
Ville Mattila wrote:
> On Tue, 15 Sep 2009, Ville Mattila wrote:
>> On Tue, 15 Sep 2009, Matthijs Mekking wrote:
>>> Of course, if you run nsdc stop, no processes should be kept alive. Is
>>> this the case?
>> Yes. 'nsdc stop' leaves xfrd process running and returns ok.
>>> What does nsdc stop output?
>> Nothing really:
>> % sudo /usr/sbin/nsdc -c
>> /v/net/ns-secondary.funet.fi/etc/nsd/nsd-isar.conf stop
>> % echo $?
> We've now worked around this problem by modifying the nsd init script
> to NOT run 'nsdc patch' before 'nsdc stop' in restarts. No problems
> in xfrd shutdown for 3+ weeks and 50+ restarts.
> So it seems running 'nsdc patch' (which can take several seconds in our
> environment) could prevent nsd/xfrd process termination by 'nsdc stop'.
> Can you confirm this? What can we do to help finding a real resolution
> to this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the nsd-users