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 b
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
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.con
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.
Vince
___
