Rich Goodson wrote:
> If you're really looking to cover all bases, there's a little gotcha in
> Solaris (even in 10) that will make this startup script fail if it's
> invoked with sh (as most startup scripts that I've seen are).
Yeah, I was trying to avoid "shell portability" concerns to try to
av
If you're really looking to cover all bases, there's a little gotcha
in Solaris (even in 10) that will make this startup script fail if
it's invoked with sh (as most startup scripts that I've seen are).
The 'test -e' is unavailable in sh on Solaris. You need to use -r
(file exists and is r
On Mar 26 2009, Kevin Darcy wrote:
[...]
The problems with using "ps" to find the named process include:
-- you can get false matches if you don't tailor your string matching
_just_right_,
-- unexpectedly "missed" matches if the command-line arguments change,
even a little bit (e.g. if someone
dev_n...@zoho.com wrote:
>
>
> > If named is invoked successfully on startup, then the contents of the
> > PID file will be overwritten with the new PID value.
> >
> > If named *isn't* invoked successfully on startup, then that's a separate
> > error condition that should be detected an
> If named is invoked successfully on startup, then the contents of the
> PID file will be overwritten with the new PID value.
>
> If named *isn't* invoked successfully on startup, then that's a separate
> error condition that should be detected and dealt with, within the whole
> sta
If named is invoked successfully on startup, then the contents of the
PID file will be overwritten with the new PID value.
If named *isn't* invoked successfully on startup, then that's a separate
error condition that should be detected and dealt with, within the whole
startup subsystem.
The
I don't agree so much.
some time when a system is reboot unnormally, named doesn't have the chance to
remove its pid file.
(when OS is shutdown normally, OS sends SIGTERM to named, named can exit and
remove its own pid file.)
after system is started, the pid number in name's pid file is maybe an
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).
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
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:
nobody28312 1 0 10:10 ?00:00:00 /usr/local/bind/sbin/name
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:
nobody28312 1 0 10:10 ?00:00:00 /usr/local/bind/sbin/named -u
nobody
nobody2835
11 matches
Mail list logo
