Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 May 2020 17:20:27 +0200
From:      Per olof Ljungmark <peo@nethead.se>
To:        freebsd-ports@freebsd.org
Subject:   Re: Bind 9.16 port error still lingers
Message-ID:  <d42f4172-8a76-719a-2794-9bf28529829f@nethead.se>
In-Reply-To: <20200502151636.GA22397@doctor.nl2k.ab.ca>
References:  <20200502140501.GA16385@doctor.nl2k.ab.ca> <20200502143210.GA4453@elch.exwg.net> <20200502151636.GA22397@doctor.nl2k.ab.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-05-02 17:16, The Doctor via freebsd-ports wrote:
> On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote:
>> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
>>
>>> Subject: Bind 9.16 port error still lingers
>>
>> "Still"?
>>
>>> May  1 21:29:02 gallifrey named[90441]: Required root permissions to open '/var/run/named.pid'.
>>> May  1 21:29:02 gallifrey named[90441]: Please check file and directory permissions or reconfigure the filename.
>>
>> Did you?
>> BTW the default location for named's pidfile on FreeBSD is
>> /var/run/named/pid.
>>
>>> May  1 21:29:02 gallifrey named[90441]: parser.c:950: REQUIRE(obj != ((void *)0) && obj->type->rep == &cfg_rep_uint32) failed, back trace
>>
>> Some (configuration) value should be an integer, but isn't.
>>
> 
> cat /var/run/named.pid
> 15640
> 
> running bind911
> 
> and ls -Fail /var/run/named.pid
> 
> -rw-r--r-- 1 root wheel 6 May 1 21:38 /var/run/named.pid

I think what The Doctor tried to point out is that the pid file needs to 
be owned by the named user, normally "bind".

If named is started the "normal" wai, i.e. "service named start" it 
should create this file with "bind" as owner.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d42f4172-8a76-719a-2794-9bf28529829f>