Package: uptimed
Version: 1:0.3.17-4
Followup-For: Bug #654830

Yes, I noticed the same strange thing recently.  It was working fine
up to a few weeks (not sure exactly when it got wrong) but now the
boot entry has been duplicated and this creates impossible values,
as initially reported:

     #               Uptime | System                                     Boot up
----------------------------+---------------------------------------------------
     1   125 days, 10:06:22 | Linux 3.2.0-4-amd64       Tue Apr 15 09:12:09 2014
->   2    91 days, 13:42:27 | Linux 3.16.0-4-amd64      Mon Apr 13 10:40:34 2015
     3    91 days, 13:42:03 | Linux 3.16.0-4-amd64      Mon Apr 13 10:40:35 2015
     4    48 days, 02:02:18 | Linux 3.16.0-4-amd64      Sun Feb 22 11:54:31 2015
     5    47 days, 14:46:20 | Linux 3.2.0-4-amd64       Wed Aug 28 20:19:25 2013
     6    45 days, 08:23:39 | Linux 3.2.0-4-amd64       Fri Jan 31 07:42:01 2014
     7    39 days, 16:04:05 | Linux 3.14-2-amd64        Wed Aug 20 16:55:10 2014
     8    37 days, 20:44:10 | Linux 3.2.0-4-amd64       Tue Oct 15 18:08:57 2013
     9    37 days, 14:26:56 | Linux 3.2.0-4-amd64       Fri Dec 13 07:30:07 2013
    10    23 days, 02:57:14 | Linux 3.14-2-amd64        Fri Oct 10 12:39:48 2014
----------------------------+---------------------------------------------------
no1 in    33 days, 20:23:56 | at                        Sun Aug 16 20:46:55 2015
    up   764 days, 06:26:42 | since                     Sat Jul  6 19:29:40 2013
  down   -27 days, -01:-33: | since                     Sat Jul  6 19:29:40 2013
   %up              103.671 | since                     Sat Jul  6 19:29:40 2013

In the above display, entries 2 and 3 really refer to the same entry but you
notice that the boot up entry is shifted by 1 second whereas the uptime is
shifted by more time.  Could this be due to the NTP date adjustment of 2
seconds that happened a few weeks ago?

All my Debian machines are exhibiting the same bug.
For instance on another machine:

     #               Uptime | System                                     Boot up
----------------------------+---------------------------------------------------
->   1   132 days, 07:56:12 | Linux 3.16.0-4-686-pae    Tue Mar  3 15:26:00 2015
     2   132 days, 07:51:13 | Linux 3.16.0-4-686-pae    Tue Mar  3 15:26:01 2015

Again, the boot up time is one second apart but the uptime is way off.

-- System Information:
Debian Release: 7.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages uptimed depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  init-system-helpers    1.22
ii  libc6                  2.19-13
ii  libuptimed0            1:0.3.17-4
ii  lsb-base               4.1+Debian8+deb7u1

uptimed recommends no packages.

uptimed suggests no packages.

-- debconf information:
  uptimed/maxrecords: 50
  uptimed/mail/address: root@localhost
  uptimed/mail/do_mail: Never
  uptimed/interval: 600
  uptimed/mail/milestones_info:


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to