root@pa:/var/log# cat /etc/debian_version
8.0
root@pa:/var/log# cat daemon.log | grep fsck
Mar 17 06:15:15 pa systemd-fsck[170]: root: Superblock last write time is
in the future.
Mar 17 06:15:15 pa systemd-fsck[170]: (by less than a day, probably due to
the hardware clock being incorrectly
Am 19.03.2015 um 09:03 schrieb pav ka:
root@pa:/var/log# cat /etc/debian_version
8.0
root@pa:/var/log# cat daemon.log | grep fsck
Mar 17 06:15:15 pa systemd-fsck[170]: root: Superblock last write time is
in the future.
Mar 17 06:15:15 pa systemd-fsck[170]: (by less than a day, probably
Control: tag -1 pending
Hello all,
The release team agreed to adding hwclock-save.service to jessie now,
and also unblocked 215-12 (d-i ack still pending), so that we can go
ahead with that. Committed to git (for master only).
Martin
--
Martin Pitt|
Hello all,
For jessie+1/experimental onward, we'll fix this properly by enabling
timesyncd by default. It won't start if ntp or similar are installed.
This will make sure that the hw clock will be updated often enough,
and we won't poke false data into it:
Martin Pitt [2015-02-16 16:41 +0100]:
For master (i. e. testing/jessie), I prepared and tested the attached
patch.
Slightly refined version 2 of the patch: renamed to
hwclock-save.service to not get mingled with util-linux'
hwclock.service.
Martin
--
Martin Pitt|
On Monday 16 February 2015 16:00:36, Michael Biebl wrote:
There is also natural drift between the system clock and the RTC.
Who is supposed to account for that? On a system with an uptime
of several months, the drift may be large enough to cause the
time to go backwards at a reboot.
On Tue, Feb 17, 2015 at 06:44:28AM +0100, Martin Pitt wrote:
Josh Triplett [2015-02-16 17:37 -0800]:
Seems like systemd could take a lesson from Debian packaging metadata
here. Every mail transport agent, rather than conflicting with every
other, has a Provides: mail-transport-agent and
Josh Triplett [2015-02-16 21:49 -0800]:
Note that openntpd and chrony both have a Provides: time-daemon, but
ntp doesn't.
Interesting. Any idea why?
No, I don't; probably just an omission. openntpd and chrony both have
an explicit Conflicts: ntp, though.
It does, it's called Alias=
On Tue, Feb 17, 2015 at 06:59:15AM +0100, Martin Pitt wrote:
Josh Triplett [2015-02-16 21:49 -0800]:
It does, it's called Alias= (man systemd.unit).
Can Alias work together with Conflicts on that alias, such that each of
several services all Alias a given virtual service and Conflicts
On Mon, 16 Feb 2015 16:41:21 +0100 Martin Pitt mp...@debian.org wrote:
For jessie+1/experimental onward, we'll fix this properly by enabling
timesyncd by default. It won't start if ntp or similar are installed.
This will make sure that the hw clock will be updated often enough,
and we won't
On Tue, Feb 17, 2015 at 12:52:20AM +0100, Michael Biebl wrote:
Am 17.02.2015 um 00:27 schrieb Josh Triplett:
On Mon, 16 Feb 2015 16:41:21 +0100 Martin Pitt mp...@debian.org wrote:
For jessie+1/experimental onward, we'll fix this properly by enabling
timesyncd by default. It won't start if
Am 17.02.2015 um 00:27 schrieb Josh Triplett:
On Mon, 16 Feb 2015 16:41:21 +0100 Martin Pitt mp...@debian.org wrote:
For jessie+1/experimental onward, we'll fix this properly by enabling
timesyncd by default. It won't start if ntp or similar are installed.
This will make sure that the hw clock
Hi,
On 17 February 2015 00:52:20 CET, Michael Biebl bi...@debian.org wrote:
Sort of. The plan here is, that the individual ntp implementations ship
a native systemd unit file, which has
Conflicts=systemd-timesyncd.service [1]
This will make sure, that if e.g. ntp is installed and enabled, ntp
Hello Eric,
Eric L. [2015-02-17 1:24 +0100]:
Perhaps just a bit too late for me, but how would package vdr be
handled, which does _optionally_ set the system clock from the TV
signal.
Note that not starting timesyncd if ntp etc. are installed is mostly
an optimization, to avoid multiple
Hey Josh,
Josh Triplett [2015-02-16 17:37 -0800]:
Seems like systemd could take a lesson from Debian packaging metadata
here. Every mail transport agent, rather than conflicting with every
other, has a Provides: mail-transport-agent and Conflicts:
mail-transport-agent, specifically because
Am 04.02.2015 um 06:00 schrieb Stefan Fritsch:
On Wednesday 04 February 2015 01:41:14, Michael Biebl wrote:
Am 31.01.2015 um 10:19 schrieb Stefan Fritsch:
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
thanks
Systemd must make sure that the system
On Mon, 16 Feb 2015, Martin Pitt wrote:
Stefan Fritsch [2015-02-13 10:32 +0100]:
Can't you agree that the best way forward for jessie is to change this in
systemd?
For jessie I'd be okay with this. I'd rather have the actual unit in
util-linux and then unmask it in systemd, but that'd
Hi,
On 13/02/15 10:32, Stefan Fritsch wrote:
Once jessie is released, the correct long-term fix can be discussed in a
more relaxed way.
As a user impacted by this issue, I would like to second this motion!
Most important is to have it work for the Debian users.
Thanks, Eric
--
I'm
Stefan Fritsch [2015-02-13 10:32 +0100]:
Can't you agree that the best way forward for jessie is to change this in
systemd?
For jessie I'd be okay with this. I'd rather have the actual unit in
util-linux and then unmask it in systemd, but that'd require even more
coordination/uploads.
I'll
On Fri, 13 Feb 2015, Martin Pitt wrote:
Control: reassign -1 util-linux 2.25.2-5
Control: severity -1 normal
I still disagree with critical:
I also disagree this should be done in the first place. But I don't
want to put myself into eternal wars and who shouds the loudest
wins, so I'll
On 13/02/2015 06:54, Martin Pitt wrote:
Control: severity -1 normal
I still disagree with critical:
- If the hardware clock is so broken that at the next boot it has an
earlier time than on the previous boot/ntpdate, then writing it
once more at shutdown isn't going to entirely fix
You really should CC the the submitter when responing.
On Tuesday 10 February 2015 09:56:28, Martin Pitt wrote:
Control: severity -1 normal
Stefan Fritsch [2015-01-31 10:19 +0100]:
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
This is severity
On Friday 13 February 2015 00:09:00, Stefan Fritsch wrote:
IMHO the only proper time to write the hardware clock is when we
know the system time is correct, i. e. after an NTP sync or when
the user sets it manually.
Even if it is decided that this is right, this would require fixing in
Control: reassign -1 systemd 215-11
Martin Pitt [2015-02-13 7:54 +0100]:
Also, under sysvinit and upstart it is util-linux which does the
hwclock - sysclock dance, thus reassigning this. We shouldn't
put this logic into different packages for different init systems.
Michael just pointed out
Control: reassign -1 util-linux 2.25.2-5
Control: severity -1 normal
I still disagree with critical:
- If the hardware clock is so broken that at the next boot it has an
earlier time than on the previous boot/ntpdate, then writing it
once more at shutdown isn't going to entirely fix this
severity 755722 grave
thanks
The attached service file (from [1]) seems to work if put into
/etc/systemd/system/hwclock.service and enabled with
systemctl enable hwclock
Please include it in the package.
Note that I will escalate this to the TC if you downgrade the severity
of this bug again
Control: severity -1 normal
Stefan Fritsch [2015-01-31 10:19 +0100]:
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
This is severity inflation according to
https://www.debian.org/Bugs/Developer#severities ; adjusting back to
original severity.
I also
On Wednesday 04 February 2015 01:41:14, Michael Biebl wrote:
Am 31.01.2015 um 10:19 schrieb Stefan Fritsch:
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
thanks
Systemd must make sure that the system clock does not go
backwards,
which
Am 31.01.2015 um 10:19 schrieb Stefan Fritsch:
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
thanks
Systemd must make sure that the system clock does not go backwards,
which causes all kinds of problems, with file systems and with other
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
thanks
Systemd must make sure that the system clock does not go backwards,
which causes all kinds of problems, with file systems and with other
software. To achieve that, systemd has to sync the system time
30 matches
Mail list logo
