Hi Simon, Am Montag, 7. November 2011 schrieb Simon Kelley: > On 05/11/11 17:21, Andreas Stempfhuber wrote: > > Package: dnsmasq > > Version: 2.55-2 > > Severity: normal > > > > Hi, > > > > I assume dnsmasq should be stopped at runlevel 0, 1 and 6 and not just > > at runlevel 1 as currently. > > > > Dnsmasq is currently listed as a process which fails to stop at > > /etc/init.d/sendsigs each time I reboot or hald the PC. It unnecessarily > > delays the shutdown. This is no longer the case after replacing > > > > # Default-Stop: 1 > > > > with > > > > # Default-Stop: 0 1 6 > > > > at /etc/init.d/dnsmasq and calling "insserv -d dnsmasq". > > > > Thanks, > > > > Andi > > Your patch reverses a change that was made in response to > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506734 with the > intention that it would speed up shutdown by relying on sendsigs to stop > dnsmasq.
interesting, the intention of the patch was to speed up the shutdown by a few (hundred) milliseconds but it does the opposite, it delays the shutdown by 10 seconds. > I wonder why sendsigs is failing to stop dnsmasq in a timely manner? Because dnsmasq requires syslog which is not available during sendsigs. The LSB header of the dnsmasq initscript contains "Required-Stop: $network $remote_fs $syslog" to make sure that the network, remote filesystem and syslog is still available during shutdown. This requirements are no longer fulfilled (or assured) when dnsmasq is stopped via sendsigs. I was able to replicate the issue by manually stopping the syslog daemon and then manually stopping dnsmasq. In this sequence dnsmasq takes a long time (longer than 10 seconds) to stop. Regards, Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
