Maintained by: NLnet Labs

Stub zone behavior

Ralph Dolmans
Tue Dec 27 10:50:06 CET 2016


Hi Mike,

I meant unbound's working directory, configurable using the "directory"
config element.

Regards,
-- Ralph

On 23-12-16 17:13, Mike Brown wrote:
> On Thu, Dec 22, 2016 at 04:22:26PM +0100, Ralph Dolmans wrote:
>> Hi Mike,
>>
>> On 21-12-16 15:12, Mike Brown wrote:
>>> I fixed the names and that took care of it, although now for some reason when 
>>> I do the "unbound-control reload", I get an extra message: "error: cannot 
>>> chdir to directory: (No such file or directory)"
>>>
>>> It doesn't seem to hurt anything, but does it indicate a problem on my end? 
>>> The message apparently originates in util/configparser.y when processing 
>>> includes.
>>
>> Make sure your working directory is inside the chroot directory.
>>
>> Regards,
>> -- Ralph
> 
> I am.
> 
> # cd /var/unbound/
> # grep -r chroot .
> ./unbound.conf: chroot: /var/unbound
> # unbound-control reload
> ok
> Dec 23 09:11:27 chilled unbound: [14103:0] notice: Restart of unbound 1.5.10.
> Dec 23 09:11:27 chilled unbound: [14103:0] error: cannot chdir to directory:  (No such file or directory)
> Dec 23 09:11:27 chilled unbound: [14103:0] notice: init module 0: validator
> Dec 23 09:11:27 chilled unbound: [14103:0] notice: init module 1: iterator
>