Hi Simon,
Am Dienstag, 8. November 2011 schrieb Simon Kelley:
> On 07/11/11 22:30, Andreas Stempfhuber wrote:
> > Maybe it's related to a change between dnsmasq 2.55 in Squeeze and 2.59
> > in SID?
>
> Indeed: from the 2.56 changelog:
>
> Ensure that dnsmasq terminates cleanly when using
> --syslog-async even if it cannot make a connection to the
> syslogd.
>
> I only write this stuff, I can't be expected to remember it too :-)
>
> The patch changes
>
> if (!entries)
> {
> close(log_fd);
> break;
> }
>
>
> to
>
> if (!entries || !connection_good)
> {
> close(log_fd);
> break;
> }
>
> in flush_log()
>
> I think that's probably a better fix for the problem you're seeing than
> the runlevel change.
yes, that's the perfect fix for the root cause of the issue. Let me see if I
can easily backport the version from SID to stable and I will give it a try.
Regarding bug #506734, I have concerns because it creates an unexpected
shutdown behavior. It assumes that the shutdown order doesn't matter. But why
is there a Required-Stop option defined by LSB and why does dnsmasq use it to
define shutdown dependencies, if they don't matter? It seems to me that this
has not been considered by the discussion.
The reason for bug #50673 was a faster shutdown by stopping the daemons in
parallel by sendsigs instead of running each shutdown script in serial. In the
meantime Debian changed the init system and is executing the shutdown scripts
in parallel, one script can no longer simply delay all others. The reason for
bug #50673 (faster shutdown) does IMHO no longer exist.
Independent of my opinion regarding bug #506734, dnsmasq is a great tool. It
is since years my first choice when I need a DNS and/or DHCP server. Many
thanks for this great software!
Cheers,
Andi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
