just a quick lists of issues I found while compiling nsd myself for
testing Wouter's fix for the bug I reported.
- When flex/bison are not installed during ./configure this just
results in:
...
checking for bison... no
checking for byacc... no
but no failure. It would be nice to catch that at configure time.
- if /var/db/nsd doesn't exist
sudo ./nsd -c ../nsd.conf
exists with status 0 and no error message. If nsd would exit with
!= 0 an init script could catch such an error. Not sure if this is
easy enough to be feasible to implement.
just a quick lists of issues I found while compiling nsd myself
for testing Wouter's fix for the bug I reported.
- When flex/bison are not installed during ./configure this just
results in:
... checking for bison... no checking for byacc... no
but no failure. It would be nice to catch that at configure time.
This is because for the released packages, the flex/bison generated
files are included (and are used if flex and bison are missing). So
it is not an error for released packages.
- if /var/db/nsd doesn't exist
sudo ./nsd -c ../nsd.conf
exists with status 0 and no error message. If nsd would exit with
!= 0 an init script could catch such an error. Not sure if this is
easy enough to be feasible to implement.
NSD forks into the background before it chroots or chdirs, and this
causes the error to be printed later. nsd-checkconf tests errors in
configuration before the daemon is started.