On 07/11/11 20:22, Andreas Stempfhuber wrote: >> 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. >
That's good information, thanks. It explains a lot. The relevant dnsmasq code is flush_log() in src/log.c - but that's supposed to exit without waiting if the connection to the syslog daemon is lost. Looks like that's not working: I'll see if I can reproduce. Cheers, Simon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
