On Thu, Nov 25, 2021 at 03:34:15PM +0800, 李菲 wrote: > On Thu, Nov 25, 2021 at 3:32 AM Marc Haber <mh+debian-packa...@zugschlus.de> > wrote: > > On Thu, Nov 11, 2021 at 06:56:33PM +0800, 李菲 wrote: > > > wrote: > > > I guess the below 'Reproduce' can tell this :) That is, if atop starts > > > before > > > atopacctd, it will read from /var/cache/atop.d/atop.acct. Instead, if > > > atopacctd > > > starts earlier, atop will read from /run/pacct_shadow.d/0000000000.paf > > > which is generated by atopacctd. > > > > Is this a race condition that only occurs once in a while? I tried it > > three times now on a test system and all three times it ended up with > > atop reading from the .paf file right after reboot. > > > You mean reboot the machine? I am wondering why rebooting > is needed after installing atop.
It is not. I just tried to reproduce your issue. > I did the following check just > after installing atop without rebooting the machine. :) > As for the reboot, I am inclined to the problem is corrected > after rebooting, mainly due to the "Before=atop.service" > in atopacct.service file. So I need to de- and reinstall atop to reproduce this? 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
