Nickolai Zeldovich
Fujitsu Network
Ian Logan
Jochen Bern
(I think I left 2 people out, sorry)
ANSWER:
Everyone basically said the same thing. in.named is a daemon that forks
itself into a background process. So when init spawns the process,
in.named forks and it appears to init that it is no longer running.
Thus, init respawns in.named again and again and again.
Don't run in.named from inittab.
A FEW OTHER NOTES:
We are running a secondary DNS server on another subnet (incase of a router
outage). It does take over when the primary goes down, but customers
notice a slow down when the primary whent down.
The primary very rarely fails. 3 times in the last year and once was my
fault when upgrading DNS server daemon.
I could hack the code and eliminate the fork(), but I will pass on this
option.
After discussing the amount of down time actuall incured by DNS crashes
and my upgrading problems, we have decided not to hack in.named to run
from inittab or write a slef checking script from crontab.
ORIGINAL POST:
>
>
>DNS crashed out and was fixed with issuing the command /usr/sbin/in.named.
>Now the boss decides I need to write a script to see if in.named is
running, if
> not restart it.
>
>
>Well, knowing more than I should, I decided the better solution to the
nonexisting problem would be
>1- comment out launching in.named from /etc/init.d/inetsvc
> #if [ -f /usr/sbin/in.named -a -f /etc/named.boot ]; then
> # /usr/sbin/in.named; echo "starting internet domain name server."
> #fi
>2- kill the /etc/in.named process
>3- add to /etc/inittab
> ns:2:respawn:/usr/sbin/in.named
>
>As soon as I save /etc/inittab, CPU utilization goes to 100% and in.named
> never gets launched
>
>
>This looked so straight forward. What am I doing wrong???
>
>
>thx
\\\|///
\\ ~ ~ //
( @ @ )
--------oOOo-(_)-oOOo--------
UNIX is friendly, it is just more particular about who its friends are.
Carl Carpenter - carlc@kivex.com - (301) 215 8201
-----------------Oooo.--------
.oooO ( )
( ) ) /
\ ( (_/
\_)