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

On Tue, 03 Aug 2010 09:44:49 -0500 John Hasler wrote: > > John, there's also the shutdown issue: we should ensure that the > > chrony stop script is executed before the hwclock stop script, during > > a shutdown. > > Same argument applies to shutdown as to startup: chrony already depends > on thi

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

> John, there's also the shutdown issue: we should ensure that the > chrony stop script is executed before the hwclock stop script, during > a shutdown. Same argument applies to shutdown as to startup: chrony already depends on things that depend on $time. However, this issue is much more complic

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

On Mon, 02 Aug 2010 10:05:51 -0500 John Hasler wrote: > I will add a dependency on hwclockfirst in the next upload but the > existing dependencies make it impossible for chrony to start before > hwclockfirst so the absence of this from 1.24-2 (uploaded 2010.07.31) is > of minor importance. All th

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

I will add a dependency on hwclockfirst in the next upload but the existing dependencies make it impossible for chrony to start before hwclockfirst so the absence of this from 1.24-2 (uploaded 2010.07.31) is of minor importance. All the other issues in 463518 have been addressed. -- John Hasler

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

implies that chrony should depend on $time, not hwclock. However, under some circumstances chrony may step the clock, causing problems for things that depend on $time and might start before chrony if it depends on $time (which evidently is hwclock by default

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

On Sun, 01 Aug 2010 15:01:49 -0500 John Hasler wrote: > I just noticed that I forgot to add hwclock to the LSB headers. I'll do > so in the next upload. Good, I am looking forward to seeing this new upload. Thanks. -- http://www.inventati.org/frx/progs/scripts/pdebuild-hooks.html Need some p

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

I notice that ntp does not have a hwclock dependency. -- 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

I just noticed that I forgot to add hwclock to the LSB headers. I'll do so in the next upload. -- 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.or

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

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?

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?

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?

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?

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?

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