Bug#779040: fake-hwclock: does not run at shutdown
On Sun, Mar 01, 2015 at 01:38:37AM +, gnubifer...@openaliasbox.org wrote: Hi Alexandre, I can confirm that adding Conflicts=shutdown.target resolves the problem. Thanks for providing a solution. (By the way, I have not added Before=systemd-journald.service as you did, because my journal correctly starts with the fake-hwclock saved timestamp, not with the 1970-01-01 that you saw.) Excellent, thanks for confirming. I'm back from vacation now, so looking to get this fixed and into Jessie. It's clearly a major bug... -- Steve McIntyre, Cambridge, UK.st...@einval.com Since phone messaging became popular, the young generation has lost the ability to read or write anything that is longer than one hundred and sixty characters. -- Ignatios Souvatzis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779040: fake-hwclock: does not run at shutdown
Package: fake-hwclock Version: 0.8 Followup-For: Bug #779040 I can confirm that Conflicts=shutdown.target resolves this issue. This is necessary because DefaultDependencies=no is used to ensure fake-hwclock starts early and restores the previous time as quickly as possible. Unless DefaultDependencies= is set to false, service units will implicitly have dependencies of type Requires= and After= on basic.target as well as dependencies of type Conflicts= and Before= on shutdown.target. These ensure that normal service units pull in basic system initialization, and are terminated cleanly prior to system shutdown. Only services involved with early boot or late system shutdown should disable this option. [1] http://www.freedesktop.org/software/systemd/man/systemd.service.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779040: fake-hwclock: does not run at shutdown
Alexandre Detiste writes: [...] here is an exercpt from the last version of this service file I found in /etc; the only things I tweaked further are the Before=systemd-journald.service because I didn't liked seeing 1970-01-01 in the journal and Conflicts=shutdown.target, this line may actually helps you solve your problem. /lib/systemd/system/systemd-timesyncd.service also includes the same Conflicts=. --- [Unit] Description=Restore / save the current clock Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=systemd-journald.service Conflicts=shutdown.target Indeed, the following patch fixes the issue I have reported for me: --- fake-hwclock.service.orig 2015-03-03 12:49:11.32451 +0100 +++ fake-hwclock.service2015-03-03 12:45:30.54823 +0100 @@ -3,6 +3,7 @@ Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=sysinit.target +Conflicts=shutdown.target [Service] EnvironmentFile=-/etc/default/fake-hwclock Your other suggestion might be useful too. Thanks to both of you for your help. Harald
Bug#779040: fake-hwclock: does not run at shutdown
Hi Alexandre, I can confirm that adding Conflicts=shutdown.target resolves the problem. Thanks for providing a solution. (By the way, I have not added Before=systemd-journald.service as you did, because my journal correctly starts with the fake-hwclock saved timestamp, not with the 1970-01-01 that you saw.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779040: fake-hwclock: does not run at shutdown
Hi, systemd has incorparted fake-hwclock -like functionality since v213 I haven't used fake-hwclock since, I guess this silly .gif is not up-to-date: https://lh3.googleusercontent.com/-bZId5j2jREQ/U-vlysklvCI/CrA/B4JggkVJi38/w426-h284/bd0fb252416206158627fb0b1bff9b4779dca13f.gif Anyway, here is an exercpt from the last version of this service file I found in /etc; the only things I tweaked further are the Before=systemd-journald.service because I didn't liked seeing 1970-01-01 in the journal and Conflicts=shutdown.target, this line may actually helps you solve your problem. /lib/systemd/system/systemd-timesyncd.service also includes the same Conflicts=. --- [Unit] Description=Restore / save the current clock Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=systemd-journald.service Conflicts=shutdown.target Alexandre Detiste http://lists.freedesktop.org/archives/systemd-devel/2014-May/019537.html The daemon saves the current clock to disk every time a new NTP sync has been acquired, and uses this to possibly correct the system clock early at bootup, in order to accommodate for systems that lack an RTC such as the Raspberry Pi and embedded devices, and make sure that time monotonically progresses on these systems, even if it is not always correct. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779040: fake-hwclock: does not run at shutdown
Hi Harald, On Sat, Feb 14, 2015 at 04:33:28PM +0100, Harald Geyer wrote: Package: fake-hwclock Version: 0.8 Severity: important Dear Maintainer, I'm using fake-hwclock on a cubieboard to keep my time monotonic. The following things work: Restoring the saved time at boot. Saving the system time once per hour. The following doesn't work: Saving the system time at shutdown or reboot. OK. This leads to fsck running everytime the system starts, because time is not monotonic. Right. I tried to look into this a bit but alas I'm not yet familiar enough with systemd to see what is going wrong. (And I won't have a serial console available in the next days.) So if you need more information to make sense of this, you will need to tell me how to aquire it. Hmmm. I'm afraid I really don't know much about systemd setup here - the systemd support came from a patch by Alexandre Detiste. Alexandre: any suggestions please? -- Steve McIntyre, Cambridge, UK.st...@einval.com Google-bait: http://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779040: fake-hwclock: does not run at shutdown
Package: fake-hwclock Version: 0.8 Severity: important Dear Maintainer, I'm using fake-hwclock on a cubieboard to keep my time monotonic. The following things work: Restoring the saved time at boot. Saving the system time once per hour. The following doesn't work: Saving the system time at shutdown or reboot. This leads to fsck running everytime the system starts, because time is not monotonic. I tried to look into this a bit but alas I'm not yet familiar enough with systemd to see what is going wrong. (And I won't have a serial console available in the next days.) So if you need more information to make sense of this, you will need to tell me how to aquire it. TIA, Harald -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.16.0-4-armmp (SMP w/1 CPU core) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fake-hwclock depends on: ii init-system-helpers 1.22 fake-hwclock recommends no packages. Versions of packages fake-hwclock suggests: ii cron [cron-daemon] 3.0pl1-127 pn ntp none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
