nsd users - Jan 2007 - nsd.conf include needs full path

When I use "include:" in nsd.conf it seems to need a full path.

I have the following line in my nsd.conf:

include: "nsd-slave.conf"

And when I do "nsd-checkconf /usr/local/etc/nsd/nsd.conf" or
any nsdc command it fails with an error:

/usr/local/etc/nsd/nsd.conf:64: error: cannot open include file 'nsd- 
slave.conf': No such file or directory

Unless I run the command in the config directory, then the config
is marked as "valid" while it realy isn't.

Could it not use the zonesdir as default path?

/Oli

--
Olafur Osvaldsson
Systems Administrator
Internet a Islandi hf.
Email: oli at isnic.is
Tel:   +354 525-5291

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

?lafur Osvaldsson wrote:
> When I use "include:" in nsd.conf it seems to need a full path.
> 
> I have the following line in my nsd.conf:
> 
> include: "nsd-slave.conf"
> 
> And when I do "nsd-checkconf /usr/local/etc/nsd/nsd.conf" or
> any nsdc command it fails with an error:
> 
> /usr/local/etc/nsd/nsd.conf:64: error: cannot open include file 'nsd- 
> slave.conf': No such file or directory
> 
> Unless I run the command in the config directory, then the config
> is marked as "valid" while it realy isn't.
> 
> Could it not use the zonesdir as default path?
> 
> /Oli
> 
Hi ?lafur,

Thanks for the bugreport.

The problem now is that it finishes reading all of the config before
looking at the zonesdir setting and changing directory.
It is possible to put the server: entry last in the file (or even a
duplicate server: entry that updates some values to different settings).
So during the config reading it does not yet change working directory.

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFFrL2/kDLqNwOhpPgRAsxBAJ0d2I4jJ3crC/R1XIR5AgaURLmBVACeJJCT
nBeoZuXnd3MBLCaRIC8FDnk=bToq
-----END PGP SIGNATURE-----