Hi Guillem, On 27.01.2012 10:18, Guillem Jover wrote: >> * rsyslog should probably switch to use s-s-d --exec instead (why is >> it using --name anyway? that option has always been more unreliable). > > Still pending. Upon your recommendation, I've switched stop() to "s-s-d --pidfile /var/run/rsyslogd.pid --exec /usr/sbin/rsyslogd", but I've run into a problem on *kfreebsd* now: To minimise downtime during upgrades, I restart rsyslogd in postinst, rather then stop in prerm/start in postinst. But s-s-d doesn't like it apparently when the binary is replaced during upgrades (seen during a squeeze → wheezy test upgrade) s-s-d --stop --pidfile /var/run/rsyslogd.pid --exec /usr/sbin/rsyslogd No /usr/sbin/rsyslogd found running, none killed. But rsyslogd is running, and when I do ls -la /proc/$(cat /var/run/rsyslogd.pid)/exe # /proc/324/exec -> unknown I don't see this behaviour on Linux. Is this a bug / special behaviour on kfreebsd? What are daemons that use restart-in-postinst supposed to use? I'm inclined to switch back to --name, as I don't remember seeing such a problem with --name. But I'd like to hear your opinion first. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature