PID-File from Bind 9.3.1

[John Wobus]

My experience with BIND 9.3 is that a normal "SIGTERM" kill results in=20=

a second or two of final housekeeping/whatever and BIND deletes the PID=20=

file after it has done this other work.  Thus if you start another BIND=20=

process too soon after a kill, the stopping process will delete the new=20=

PID file.

John Wobus
Cornell CIT

On Apr 14, 2005, at 4:55 AM, Tom Schmitt wrote:

> Hi,
>
> I use Bind 9.3.1 on Solaris 2.8.
>
> In a case of desaster-recovery one of my secondary DNS-Server stops =
and
> starts with a new (primary) config. A simple reload is not enough=20
> because he
> has new interface to listen on.
>
> My problem: Most times, when I test ist and stop and restart the=20
> server, all
> things work out, but the named didn't write the named.pid-file whrere
> normally his pid could be found.
>
> He has all rights to write in this directory and I don't find any
> error-message in the Logfiles, even on Debugmod there is nothing.
>
> Has anyone any idea what coult causse the named not to write his=20
> pid-file?
>
> =46rom my named.conf:
>> options {
>>         pid-file "/var/run/named.pid";
>
> and ls -la /var/run/ give:
> drwxrwxrwx   2 named    bind        1024 Apr 14 10:29 .
>
> Second question:
> Could there occur any additional problem if the pid-file is missing?
>
>
> thanks,
> Tom.
>
> --=20
> +++ GMX - Die erste Adresse f=FCr Mail, Message, More +++
>
> 1 GB Mailbox bereits in GMX FreeMail http://www.gmx.net/de/go/mail
>
>