On Wed, 16 Nov 2011, Phil Mayers wrote:
> It might be good if bind were able to re-start itself, rather than dying
> outright (e.g. re-exec the process) but that is dangerous too; it's better
> done by an unrelated supervising process.
In the bind9 tarball's contrib directory there is a simply "n
On Thursday 17 November 2011 15:24:12 Jeremy C. Reed wrote:
> Also what other types of nanny scripts do you use? (I already saw
> other emails with a few suggestions.)
Mine is a very trivial thing, basically just:
/sbin/pidof named || restartNamed
where "restartNamed" is a function to log the
On 11/17/11 1:45 PM, "/dev/rob0" wrote:
> What I should perhaps do: separate the authoritative named instance
> from the recursive one on the mail server. I suppose BIND 10 does
> this, by design?
Yes, that is best practice (I keep reading it in docs from people I trust,
like Cricket Liu). I've
On 11/17/2011 13:24, Jeremy C. Reed wrote:
> Also what other types of nanny scripts do you use? (I already saw other
> emails with a few suggestions.)
Personally I have always thought that the perl script in contrib is
overly complex.
#!/bin/sh
while : ; do
/path/named -f
sleep
> Personally I have always thought that the perl script in contrib is
> overly complex.
>
> #!/bin/sh
>
> while : ; do
> /path/named -f
> sleep 17
> done
That works, but note that it won't catch the problem if named hangs.
Running it in xinetd works too, but same note.
--
Evan Hu
On 11/18/2011 11:48, Evan Hunt wrote:
>> Personally I have always thought that the perl script in contrib is
>> overly complex.
>>
>> #!/bin/sh
>>
>> while : ; do
>> /path/named -f
>> sleep 17
>> done
>
> That works, but note that it won't catch the problem if named hangs.
Right, but t
6 matches
Mail list logo
