Hello Xiscu,
Maybe "uptimed" fits better for you. It have a daemon that records
statistics about a machine's uptime, consequently, under suspend and
hibernate, the daemon doesn't run. Try their behaviour and see...
Thanks,
Hello Xiscu,
The only reference nowadays inside the kernel for the uptime is the
efective "uptime" variable accesible through /proc/uptime, it have the
following definition:
uptime Wall clock since boot, combined idle time of all cpus
To cover your use case, at least, is needed an other varia
Hi Ricardo,
hum ... in that case, please feel free to close the issue. but just
curiosity on the feature: does that means that's a kernel feature ?
meaning the kernel should, equivalent to 'btime', have for e.g. 'stime'
and 'htime' counters ?
Thanks in advance!
--xiscu
On 11/15/18 4:34 PM, Ricar
Hi Xiscu,
Tuptime can't achieve that behaviour, is not possible.
Thanks,
Hi Ricardo,
On 11/8/18 3:40 PM, Ricardo Fraile wrote:
> But in any case, the time counted is not the "running time", the term
> "wall clock" or "elapsed real time" is more correct instead of the
> actual definition, I will fix it.
Wouldn't be also possible to sample the "wall clock" at a given
fr
Hello Xiscu,
The design of Tuptime is dependent of the information that the kernel
report in the uptime and btime counters from /proc/uptime and /proc/stat
respectively.
Both (documented under Documentation/filesystems/proc.txt) are related
with the boot time date and none of them are reset
Package: tuptime
Version: 3.4.0
Severity: wishlist
Tags: upstream
Dear Maintainer,
please add support for the suspend and hivernate states.
The rationale is that while the computer unit measured
isn't used or runnning on those states, that time (seems?)
to count as running time.
Thanks in advanc
7 matches
Mail list logo
