Bug#785419: Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2021-05-09 Thread Rick Thomas
On Sat, May 8, 2021, at 12:02 PM, Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > > Hi, > > Ist this still an issue or has been fixed in meanwhile? I'm going > through some older src:linux associated buts and noticed that it was > considered here to reassign it to util-linux. > > Is

Bug#785419: Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2021-05-08 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo Hi, Ist this still an issue or has been fixed in meanwhile? I'm going through some older src:linux associated buts and noticed that it was considered here to reassign it to util-linux. Is the problem still present? Further: On Fri, Mar 17, 2017 at 07:55:31PM +0100,

Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2020-12-27 Thread Chris Hofstaedtler
Hi, * Lukas Wunner : > Back in 2011, hwclock-set was amended to bail out if systemd is present. > According to #629811 the rationale was that "systemd > 25 sets the > hwclock itself, based on the contents of /etc/adjtime, so > /lib/udev/hwclock-set should not do anything if running under systemd."

Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2018-08-27 Thread launchpad_sge4
I also had a look at https://github.com/mattwire/upspico/tree/master/systemd . But I think it is not needed to write the system clock to rtc on shutdown, because systemd-timesyncd or timedatectl (dont know which of those is actually getting ntp sync and write to rtc) are updating the rtc after e

Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2018-07-22 Thread Heinrich Schuchardt
Having systemd installed does not imply that the system is connected to a network at regular time intervals. So solely relying on NTP is not a good decision. The systemd scripts at https://github.com/mattwire/upspico/tree/master/systemd solve the problem for me. Why shouldn't we do the same (a on

Bug#785419: Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2017-03-17 Thread Lukas Wunner
[cc += pkg-sysvinit-de...@lists.alioth.debian.org, pkg-systemd-maintain...@lists.alioth.debian.org, debian-ker...@lists.debian.org, debian-de...@lists.debian.org (as requested by Andreas Henriksson)] [cc += #785445, #785419, Rick Thomas (bug reporter)] Hi Andreas, sorry for t

Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2017-02-28 Thread Andreas Henriksson
Hello Lukas Wunner, Thanks for following up with both a new proposal and patch! On Mon, Feb 27, 2017 at 02:34:34PM +0100, Lukas Wunner wrote: [...] > Okay, let's define a policy first. How about: > > (1) Users can set HWCLOCKACCESS=no in /etc/default/hwclock to prohibit > setting the system

Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2017-02-27 Thread Lukas Wunner
On Sun, Feb 26, 2017 at 07:56:06PM +0100, Andreas Henriksson wrote: > > But this doesn't work if the driver for the RTC is compiled as a module > > or if the kernel was compiled with CONFIG_RTC_HCTOSYS disabled. > > Second (easy) case first, if CONFIG_RTC_HCTOSYS is disabled then > I think we shou

Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2017-02-26 Thread Andreas Henriksson
Hello Lukas Wunner, Thanks for your bug report. On Wed, Feb 15, 2017 at 01:55:30PM +0100, Lukas Wunner wrote: > Back in 2011, hwclock-set was amended to bail out if systemd is present. > According to #629811 the rationale was that "systemd > 25 sets the > hwclock itself, based on the contents of

Bug#855203: hwclock-set: Synchronize from hwclock despite systemd presence

2017-02-15 Thread Lukas Wunner
Package: util-linux Version: 2.19.1-5 Severity: important Tags: patch Back in 2011, hwclock-set was amended to bail out if systemd is present. According to #629811 the rationale was that "systemd > 25 sets the hwclock itself, based on the contents of /etc/adjtime, so /lib/udev/hwclock-set should n