Hi Markus,
thanks and keep up the good work :-).
Kind regards
Harald Jenny
Hi Harald,
I have included your simple fix in git for the next release:
https://salsa.debian.org/dns-team/nsd/commit/ea3dafa968dbc3768184fda5da9cc9c3c3506c83
Thanks!
Best regards,
Markus
Hi,
> The nsd-checkconf approach seems most robust to me.
I guess so too.
> but in general,
> pidfiles are an abomination, and any robust supervisor should already be
> able to keep track of the processes that it has spawned in the past.
Well they are a relict of the past times where everythin
On Mon 2018-10-29 14:07:33 +0100, har...@a-little-linux-box.at wrote:
> It seems the problem with the initscript is my chrooted nsd setup, if
> PIDFILE is not defined in the initscript it automatically gets set to
> /var/run/$NAME.pid (which is not true in a chrooted setup). So I guess
> adding the
It seems the problem with the initscript is my chrooted nsd setup, if PIDFILE
is not defined in the initscript it automatically gets set to
/var/run/$NAME.pid (which is not true in a chrooted setup). So I guess adding
the PIDFILE line in the initscript is not a general need but just for people
5 matches
Mail list logo
