On Thu, Nov 02, 2017 at 12:05:25PM +, Jonathan Dowland wrote:
This bug is now at least 5 years old and IMHO seems to suggest that the package
simply does not work. Should we consider dropping it?
Indeed the bug is old, but the package works fine in most situations.
# Upt
Just to add to the mix, this is on a NAS which has never been suspended:
# Uptime | System Boot up
+---
-> 1 142 days, 12:48:22 | Linux 3.16.0-4-amd64 Tue Jun
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:
#
Possible cause of duplicate entries is that uptimed on linux takes
bootid from "btime" line in /proc/stat and uses that value to
identify entries. If I understand correctly, this value is
essentially a difference between CLOCK_REALTIME and CLOCK_BOOTTIME.
It's neither constant nor a good estimate
Package: uptimed
Version: 1:0.3.17-3.1
Followup-For: Bug #654830
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of
Further confirmation, this happens on all of my servers on this
version, including this doozy from a new system:
andrew@opvpn:~$ uprecords
# Uptime | System Boot up
+-
On Fri, Jan 06, 2012 at 12:59:38AM +0100, Axel Beckert wrote:
> The first entry seems to be duplicated more or less, leading to wrong
> uptime percentage (115%) and wrong downtime (-2 days).
Just in case further confirmation is needed, I'm experiencing the same
bug on my laptop:
zack@usha:~$ up
severity 654830 minor
tags 654830 upstream
quit
Hi,
The uptime percentage and dowtime values are bogus, upstream is aware
of that and I believe they will be removed in the next release.
The double entry is puzzling though, thanks for reporting. I wonder if
that's just the addition of the curren
Package: uptimed
Version: 1:0.3.16-3.2
Severity: normal
Hi,
on a netbook which I suspend to RAM quite often (not sure if that's
relevant :-), I found the following strange output of uprecords:
$ uprecords
# Uptime | SystemBoot up
---
9 matches
Mail list logo
