Standard methodology would be to read the contents of the PID file and
see if that process is running (traditionally kill -0 $pid can be used
to non-intrusively check whether a given process is running).
- Kevin
dev_n...@zoho.com wrote:
That's the good idea, I have written a script to archive that:
start()
{
if ! ps -efw|grep 'named -u nobody'|grep -v grep >/dev/null 2>&1;then
/usr/local/bind/sbin/named -u nobody
fi
}
Thanks.
> dev_n...@zoho.com wrote:
> > Hello,
> >
> > I found a strange case on bind server.
> > when one named was running, I started another one or more (the same) named server again, they all got started successsfully.
> >
> > this is the ps output:
> >
> > nobody 28312 1 0 10:10 ? 00:00:00 /usr/local/bind/sbin/named -u nobody
> > nobody 28359 1 0 10:16 ? 00:00:00 /usr/local/bind/sbin/named -u nobody
> > nobody 28362 1 0 10:16 ? 00:00:00 /usr/local/bind/sbin/named -u nobody
> >
> > But at this time named server behaves not normal.
> > for example, I added a NS record and execute rndc reload, the new record could not be queried.
> >
> > why this happen?
> >
> >
> Do you have a wrapper script that checks whether there is already a
> named instance running before starting another one?
>
> Starting named manually without some sort of wrapper script like that is
> dangerous business, the instances have a high possibility of fighting
> with each other over the listen port, with the end result often being
> that *none* of them are functional. Look at your logs, you'll probably
> find some ugliness there.
>
>
> - Kevin
>
> _______________________________________________
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
