Bug#463518: Can we mitigate this bug with appropriate LSB init headers?

2010-06-26 Thread Francesco Poli
On Mon, 22 Mar 2010 20:14:47 -0500 John Hasler wrote: > The 1.24 release, which I hope get out within a week, will include a > version of your patches. This, along with changes we have made > upstream, will hopefully solve this problem once and for all. I've just noticed that chrony/1.24-1 has b

Bug#463518: Can we mitigate this bug with appropriate LSB init headers?

2010-03-22 Thread John Hasler
The 1.24 release, which I hope get out within a week, will include a version of your patches. This, along with changes we have made upstream, will hopefully solve this problem once and for all. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to debian-bugs-dist-re

Bug#463518: Can we mitigate this bug with appropriate LSB init headers?

2010-03-22 Thread Francesco Poli
On Tue, 17 Nov 2009 18:44:39 -0600 John Hasler wrote: > Thank you. Hi again John. Is there any progress on applying my cumulative patch? http://bugs.debian.org/463518#30 -- http://www.inventati.org/frx/progs/scripts/pdebuild-hooks.html Need some pdebuild hook scripts? ...

Bug#463518: Can we mitigate this bug with appropriate LSB init headers?

2009-11-17 Thread John Hasler
Thank you. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#463518: Can we mitigate this bug with appropriate LSB init headers?

2009-11-17 Thread Francesco Poli
tags 463518 + patch tags 407466 - patch thanks On Sun, 15 Nov 2009 16:44:35 +0100 Francesco Poli wrote: [...] > I think that adding a > > Should-Start: $named > > to the LSB init headers of /etc/init.d/chrony could mitigate this bug. > > What do you think? > Is it a good idea? I for

Bug#463518: Can we mitigate this bug with appropriate LSB init headers?

2009-11-15 Thread Francesco Poli
Hi John, I think I am experiencing a problem which seems to be closely related to this problem. On a box where /etc/resolv.conf is: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OV