Maintained by: NLnet Labs

Relative path for include and *-file

W.C.A. Wijngaards
Mon Oct 2 11:10:42 CEST 2017


Hi Newell,

On windows, the directory is the directory of the exe file.   Set that
as the working directory before starting unbound.

So, set the paths relative to the location of unbound.exe.

Best regards, Wouter

On 26/09/17 14:47, Newell Zhu via Unbound-users wrote:
> Hi
> 
> I face a problem about relative path in unbound.conf
> 
> In unbound.conf, we can include other config file with
> include: directive. It’s work for absolute path.
> 
> But how can I use relative path?
> 
> Actually I have read the description about include: directive
> 
>> relative pathnames for the included names work if the directory where
> the daemon is started equals its chroot/working directory or is
> specified before the include statement with directory: dir.
> 
> 
> But what is the default working directory for unbound 1.6.5 on Windows
> 7?(Yes, I use windows.)
> 
> I research google about “Windows unbound default working directory”
> and “Windows unbound include: directive” but no result.
> 
> In one word, How can I use relative path for include: directive? Or does
> environment variable supported in unbound.conf, with which I use used to
> build the absolute path?
> 
> Thank you in advance for any help or advice.
> 
> Regards,
> Newell Zhu
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20171002/03138eae/attachment.sig>