|
From: Charles W. <web...@op...> - 2006-10-24 16:06:54
|
>On 23/Oct/2006 17:10 Charles Whitaker wrote .. >> > > >> >> That's what /var/run/named.pid contains -- the PID of the >> named >> >> process. >> >> >> > >> >> >> >Is the PID file setting on the Module Config page also set to >> >> >> >/var/run/named.pid ? >> >> >> >> >> >> Yes, it is. >> >> > >> >> >Ok .. so even though Webmin tries to stop BIND, it is still running >> >> >(but hung). >> >> >What do you have on the Module Config page in the 'Command to stop >> >> >BIND' field? >> >> >> >> "Just kill process" is selected. >> > >> >So does that BIND process die if you run : >> > >> >kill `cat /var/run/named.pid` >> > >> >? >> >> Yes, and another named process immediately starts. Hmmm...that's an >> interesting clue. Doesn't sound like a BIND problem so much as OS X >> restarting BIND without being asked...right? > >That would certainly explain it! I'm not too familiar with OSX, but I heard >that more recent versions introduced a new 'launchd' daemon that manages >processes .. perhaps it is responsible? > >If so, Webmin's default configuration should call launchd to shut down >BIND, rather than just killing the process. Jamie, Thanks for your help with this. I'll let you know what we find with OS X. -- Charles Whitaker Webmaster Open Door Networks |