Hi.. I'm testing nsd for use with around 55000 zones (primary named servers). i was making the big initial amout of zonetransfers, when my axfr master reloaded... now i have a nsd-xfer hanging around.. and nsdc update will never stop.. lappy# ps auxwww | grep nsd djam 45775 82.9 0.1 2468 1420 p7 R+ 1:07PM 27:38.97 /usr/local/sbin/nsd-xfer -z daxxx.dk -f /etc/nsd/gdns/daxxx.dk.axfr -s 0 194.192.xx.xxx x's to protect the innocent's ;) it's like nsd-xfer is not able to detect the broken transfer and exit? it just hangs around.. FreeBSD: 5.3 NSD 2.2.0 (not from ports) regards, Peter
On Thu, Feb 03, 2005 at 01:51:19PM +0100, Peter Larsen <mail at czar.dk> wrote a message of 26 lines which said:> it's like nsd-xfer is not able to detect the broken transfer and > exit? it just hangs around..May be the patch in http://www.nlnetlabs.nl/bugs/show_bug.cgi?id=94 will help you? Warning: I have not tested it on a production machine.
[Quoting Stephane Bortzmeyer, on Feb 3, 22:41, in "Re: minor bug in nsd ..."]> On Thu, Feb 03, 2005 at 01:51:19PM +0100, > Peter Larsen <mail at czar.dk> wrote > a message of 26 lines which said: > > > it's like nsd-xfer is not able to detect the broken transfer and > > exit? it just hangs around.. > > May be the patch in http://www.nlnetlabs.nl/bugs/show_bug.cgi?id=94 > will help you? Warning: I have not tested it on a production machine.I've looked at the patch and it seems to me that it addresses the problem properly. Thanks Stephane! Erik, the current maintainer of NSD, is moving into a new house and is off-line for a long weekend. Before we can provide a new release with this patch, rigid testing of the patch on the various platforms is required. So, this may take a few more days. In the meantime, Peter might try whether Stephane's patch works for him (and please report)? Regards, -- ted