Package: atop
Version: 2.2.5-1~exp1
Severity: normal
When using "atop" on a machine that's not running 24/7, the cronjob at
00:00 is not run more often than not (depending on your usage pattern, of
course ;). This makes some use of "atop" harder than necessary; "atop -r y"
doesn't work, you'll need the right amount of "y"esterdays to find the
right file.
So, either
1) the cronjob could be smarter, to check whether the date has
changed (and then would need to run every minute?),
2) or "atop" could be handling that (just open the file for every write,
ie. by default every 600 seconds, with the correct path newly calculated),
3) or things like suspend/resume could signal atop to start a new file.
I guess option 2 would be the easiest one to implement, and the most likely
to be correct.
Thank you for your consideration!
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages atop depends on:
ii init-system-helpers 1.46
ii initscripts 2.88dsf-59.8
ii libc6 2.24-8
ii libncurses5 6.0+20161126-1
ii libtinfo5 6.0+20161126-1
ii lsb-base 9.20161125
ii zlib1g 1:1.2.8.dfsg-4
Versions of packages atop recommends:
ii cron [cron-daemon] 3.0pl1-128
atop suggests no packages.
-- no debconf information
