On Wed, 21 Nov 2018 17:49:40 +0100, Marc wrote in message <20181121164940.ga9...@drop.zugschlus.de>:
> tags #913364 moreinfo unreproducible > thanks ..huh? Simply install and run atop's systemd cron on e.g. a freshly installed sysv box like I did, e.g. on a Devuan Ascii box. > On Sun, Nov 18, 2018 at 01:27:53AM +0100, Adam Borowski wrote: > > It has the potential to bring down the system, thus one could even > > argue upon a RC severity, but they accumulate so slowly (apparently > > two per day) and take so little resources that I wonder what could > > have slowed down Arnt's machine so badly. I've waited past only a > > single midnight though, so it's possible badness accumulates > > superlinearly. ..nah, all it takes is setting up systemctl restart loop cronjobs to juuust carry on looping. > The script kills of any existing atop process and then replaces itself > with a new instance. That's the same on systemd and on non-systemd > systems. Disabling the cron job will prevent atop's log rotation > mechanism from working. This is a bit hard to understand, I fell into > this issue myself years ago. ..in my case, simply killing the cron job loop and commenting it out, killed it totally, so I can fix our #262 later when I have the time. (Feel free to beat me to it.) > The original bug reporter has yet failed to say what's going wrong > here. I am tired of running after poorly worded bug reports. ..which part of:" # daily restart of atop at midnight 0 0 * * * root if [ -d "/run/systemd/system" ]; then systemctl \ restart atop; else /usr/share/atop/atop.daily \& ; fi" "on a non-systemd box" did you miss? > Adam, what exactly has the potential to bring down the system? ..the cron job _loops_, because it cannot for very good reasons find /run/systemd/system nor systemctl, and therefore _loops_. > Greetings > Marc, who has already wasted an hour of time to understand what's the > fscking complaint here ..this bug is insisting on assuming systemctl etc systemd commands and totally disregarding the fact some of us throw out junk "init" binaries and move on with ye aulde relics that just works, and fix atop in https://bugs.devuan.org//cgi/bugreport.cgi?bug=262 when we get such clear wont-fix hints in Message #15. ..if you Debian etc systemd guys _do_ wanna fix your #913364, put back in the test for systemd and install atop.cronsystemd if you find systemd on your boxes, and give the rest of us back our beloved atop.cronsysv. Etc. Easily found in your well documented $favorite_mirror/debian/pool/main/a/atop/atop_*tar* balls. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case.
