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
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
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
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
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
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
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
7 matches
Mail list logo
