Binary package hint: dansguardian
When you run /etc/init.d/dansguardian restart
it doesn't actually restart dansguardian. Here's why:
look at the first start-stop-daemon line. See how it ends in "--pidfile \"
and how the next one doesn't start with the name of the pidfile,
but rather with a misplaced "--retry 15" flag?
So, when you try to restart, it can't find the PIDfile, and doesn't
stop the process. The start then fails, leaving you with the old
un-restarted incarnation of dansguardian.
restart|force-reload)
#
# If the "reload" option is implemented, move the "force-reload"
# option to the "reload" entry above. If not, "force-reload" is
# just the same as "restart".
#
echo -n "Restarting $DESC: "
log_daemon_msg "Restarting $DESC: "
start-stop-daemon --stop --quiet --retry 15 --oknodo --pidfile \
--retry 15 /var/run/$NAME.pid --exec $DAEMON || log_end_msg 1
start-stop-daemon --start --quiet --pidfile \
/var/run/$NAME.pid --exec $DAEMON || log_end_msg 1
log_end_msg 0
;;
... found this bug after my daughter was in tears of frustration at being unable to watch something on youtube, and I was climbing a tree, wondering why nothing I did had any effect on the behaviour of Dansguardian...
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: dansguardian 2.10.1.1-2
ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
Date: Thu Dec 2 19:33:09 2010
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: dansguardian
TEST CASE: Install dansguardian, it initially won't run. Edit /etc/dansguardian/dansguardian.conf so it can start, then start the daemon (/etc/init.d/dansguardian start).
Restart the daemon (/etc/init.d/dansguardian restart). It will fail with an error like "Restarting DansGuardian: Restarting DansGuardian: : failed!".
Install the updated package from maverick-proposed.
Restart the daemon again. This time is will succeed.
This is an odd one as the init in the source package is correct, but I inspected the amd64 binary and it's as you described.