Package: uptimed
Version: 1:0.3.17-3.1
Severity: normal
Dear Maintainer,
I use uptimed/uprecords on different machines with different architectures.
With Linux everything works as expected. With kFreeBSD the statistics seems
to be frozen.
The first record is persistent after a reboot. The actual running time does
not survive a reboot.
Example:
fz@vorlon:~$ uprecords
# Uptime | System Boot up
----------------------------+---------------------------------------------------
-> 1 0 days, 16:47:29 | GNU/kFreeBSD 9.0-2-amd64 Sun Dec 23 21:09:01 2012
2 0 days, 00:20:00 | GNU/kFreeBSD 9.0-2-amd64 Tue Nov 6 19:38:46 2012
----------------------------+---------------------------------------------------
NewRec 0 days, 16:27:28 | since Sun Dec 23 21:29:01 2012
up 0 days, 17:07:29 | since Tue Nov 6 19:38:46 2012
down 47 days, 01:10:15 | since Tue Nov 6 19:38:46 2012
%up 1.494 | since Tue Nov 6 19:38:46 2012
This #2 record is highest running time after every reboot.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 9.0-2-amd64
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages uptimed depends on:
ii debconf [debconf-2.0] 1.5.48
ii dpkg 1.16.9
ii libc0.1 2.13-37
ii libuptimed0 1:0.3.17-3.1
ii lsb-base 4.1+Debian8
uptimed recommends no packages.
uptimed suggests no packages.
-- debconf information:
uptimed/mail/do_mail: Never
uptimed/mail/address: root@localhost
uptimed/mail/milestones_info:
uptimed/maxrecords: 50
uptimed/interval: 60
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
