Hi Philipp, thanks for your bug report.
On Mon, Dec 19, 2016 at 07:17:23PM +0100, Ph. Marek wrote: > 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. I do agree. I will forward this upstream for consideration for a later release. I will, however, only do this after a more current atop has arrived in testing - as this behavior is not a regression, which means that the issue you're reporting won't be fixed in time for stretch anyway. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
