On 13/11/11 17:06, Andreas Stempfhuber wrote:
> Hi Simon,
> 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
> d
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
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
Hi Simon,
Am Montag, 7. November 2011 schrieb Andreas Stempfhuber:
> Hi Simon,
>
> Am Montag, 7. November 2011 schrieb Simon Kelley:
> > On 07/11/11 20:22, Andreas Stempfhuber wrote:
> > > I was able to replicate the issue by manually stopping the syslog
> > > daemon and then manually stopping dn
Hi Simon,
Am Montag, 7. November 2011 schrieb Simon Kelley:
> On 07/11/11 20:22, Andreas Stempfhuber wrote:
> > 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) t
On 07/11/11 20:22, Andreas Stempfhuber wrote:
>
> 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.
>
I can't replicate this behaviour: I tried datagram an
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"
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.
> >
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
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
10 matches
Mail list logo
