Bug#2081: named does not start
Michael Alan Dorman writes (Bug#2081: named does not start): In message [EMAIL PROTECTED], Jean-Marc Bourguet w rites: PS=`ps -p $PID 2/dev/null| tail -1 | grep named` You might want to make this PS=`ps -p $PID 2/dev/null| tail -1 | grep named | grep -v grep` so that it doesn't pick up the grep process as well. Don't do things like this in production code. What if some poor user's process happens to contain the string `named' ? This is what programs like start-stop-daemon are for. (I'm glad to see that the package maintainer has fixed the problem, I'm just pointing out that this kind of trick with ps may be all very well for a quick hack, but that Debian isn't just a quick hack.) Ian.
Bug#2081: named does not start
In message [EMAIL PROTECTED], Jean-Marc Bourguet w rites: PS=`ps -p $PID 2/dev/null| tail -1 | grep named` You might want to make this PS=`ps -p $PID 2/dev/null| tail -1 | grep named | grep -v grep` so that it doesn't pick up the grep process as well. Mike. -- I thought I'd something more to say.
Bug#2081: named does not start
Package: bind Version: 4.9.3-BET-1 From time to time, named didn't start when booting. After some search, I've found that it was when fsck checked the disks. The problem was caused by the code in ndc which checks the presence of named: it checks only the presence of a process with the PID in /var/run/named.pid. So I suggest to change the line 19 of /usr/sbin/ndc PS=`ps -p $PID 2/dev/null| tail -1 | grep $PID` by PS=`ps -p $PID 2/dev/null| tail -1 | grep named` so that only a process called named with the right PID will cause ndc thinks that named is running. -- Jean-Marc Bourguet PS: Please, send any related mail to [EMAIL PROTECTED] as this system is not correctly set up yet (The reply-to field is correctly set).
