Hello Nsd,
We ran in to the error in the subject recently. The error was caused by
a partial write. However i wanted to ask a couple of questions. We
fixed the problem by removing the ixfr.db file and restarting nsd. Is
this the correct way to fix things or is there a more elegant solution.
Secondly is there anyway to check the state of this file.
Thanks John
Hi John,
Hello Nsd,
We ran in to the error in the subject recently. The error was
caused by a partial write. However i wanted to ask a couple of
questions. We fixed the problem by removing the ixfr.db file and
restarting nsd. Is this the correct way to fix things or is there
a more elegant solution.
Yes this is the correct fix.
More elegant is nsdc patch ; which also deletes ixfr.db (but it must
not have been partially written), and updates the main nsd.db with its
contents. You could run nsdc patch from cron, for example.
Secondly is there anyway to check the state of this file.
The cron job is the best way to keep the filesize down. If your
filesystem simply cannot handle the size of the files then I do not
know a nice solution with NSD3.
With NSD4 there is a feature that saves disk space, the NSD4 version
in development (in code repository), has a feature where you can set
database: "" and then it does not use the nsd.db file on disk and this
may save you a lot of disk space. NSD4 would also not make ixfr.db,
but store similar contents in /tmp/nsd.<pid>/ , but also delete those
files when it has done working with them (which may save only a little
disk space).
Best regards,
Wouter