[systemd-bugs] [Bug 65616] New: Systemd does not take clock changes into consideration when calculating service running time

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=65616

          Priority: medium
            Bug ID: 65616
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Systemd does not take clock changes into consideration
                    when calculating service running time
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: rhladik at tfc.cz
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Systemd version: systemd-44-24.fc17.x86_64 , OS: Fedora 17.

Systemd reports wrong information about service runtime because of clock change
during boot process.

[root at higgs ~]# systemctl status -- '-.mount'
-.mount - /
          Loaded: loaded
          Active: active (mounted) since Fri, 09 Mar 2012 03:57:30 +0100; 1
years and 3 months ago
           Where: /
            What: /dev/md127
          CGroup: name=systemd:/system/-.mount

[root at higgs ~]# uptime
 19:12:24 up 63 days, 22:15,  6 users,  load average: 0.43, 0.30, 0.25

The system clock were off by cca a year when the system booted and this has
been corrected via ntp daemon (chrony-1.27-0.3.pre1.fc17.x86_64).

I think that at least the "xxx ago" part of timing information should not be
affected by clock changes the same way uptime isn't.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130610/6449fcb7/attachment.html>