newsyslog and chrooted bind on 5.3

[Vince Hoffman]

On Sat, 20 Nov 2004, Ruben de Groot wrote:

> On Sat, Nov 20, 2004 at 07:45:56AM +0100, Kees Plonsz typed:
>> Vince Hoffman wrote:
>>
>>> Hi all,
>>>  since i updated my server to 5.3 and went with the default option
>>> of chrooting bind, anytime named recives a HUP signal it dies. Is this
>>> expected ? its a bit of a bugger as i will have to use cron and a short
>>> shell script instead of an entry in newsyslog.conf.
>
> You can let bind log through the syslog facility. I think that's even the
> default. That way there's no need to "HUP" named.
>

Thanks for the reply, I'll go back to letting syslog do its job i guess 
;) 
I only had it logging to files to try and separate some statistics at one 
point.

Vince

>>> Vince
>>
>> There was a discussion about that a few hours ago.
>> Use "/etc/rc.d/named restart" instead.
>
> That won't work with newsyslog. newsyslog needs a pidfile to send a HUP
> to the logging proces after the logs are rotated.
>
> Ruben
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>