We were having the same problems here and it turned out that when cupsd
was spawning off the cups-polld process, it was still running as root,
so although cupsd was running as cupsys, cups-polld was running as root.
When the init script killed cupsd (either though stop or restart), the
cups-polld process was not killed. After many restarts, there could be
several of these processes churning along in the background. The
solution is (hopefully) simple. I've patched my init script to run the
cupsd daemon initially as the cupsys user. I didn't experience any other
issues related to this on our setups, but I'll continue testing. Our
environment is Ubuntu Edgy with cupsys 1.2.4-2ubuntu3.
--- cupsys.orig 2006-10-09 12:54:23.000000000 -0400
+++ cupsys 2006-12-05 15:43:22.000000000 -0500
@@ -3,6 +3,7 @@
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/cupsd
NAME=cupsd
+CHUID=cupsys
PIDFILE=/var/run/cups/$NAME.pid
DESC="Common Unix Printing System"
@@ -46,7 +47,7 @@
modprobe -q ppdev || true # for ISO-1284 device name detection
fi
- start-stop-daemon --start --quiet --oknodo --pidfile "$PIDFILE" --exec
$DAEMON
+ start-stop-daemon --start --quiet --oknodo --chuid ${CHUID} --pidfile
"$PIDFILE" --exec $DAEMON
log_end_msg $?
;;
stop)
@@ -57,7 +58,7 @@
restart|force-reload)
log_begin_msg "Restarting $DESC: $NAME"
if start-stop-daemon --stop --quiet --retry 5 --oknodo --pidfile
$PIDFILE --name $NAME; then
- start-stop-daemon --start --quiet --pidfile "$PIDFILE" --exec
$DAEMON
+ start-stop-daemon --start --quiet --chuid ${CHUID} --pidfile
"$PIDFILE" --exec $DAEMON
fi
log_end_msg $?
;;
--
multiple cups-polld running simultaneously
https://launchpad.net/bugs/67680
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
