Bug#789690: atop process ends up in cron.service's cgroup

On Tue, Oct 04, 2016 at 08:26:53PM +0100, Sam Morris wrote: > Another pattern I have seen used by a couple of packages is to ship a > .timer and a .service file to perform the regular task, and a > corresponding cron job that invokes the same command when the system is > not booted with systemd.

Bug#789690: atop process ends up in cron.service's cgroup

On Wed, Oct 05, 2016 at 09:39:00AM +0100, Sam Morris wrote: > No problem--but I'm talking about debian/atop.cron.d; upstream's cron > files are not used by the package (the choice between systemd/sysv is > made at install time if you're using upstream's own cron jobs). Idiot me. Then, please a

Bug#789690: atop process ends up in cron.service's cgroup

On Wed, 2016-10-05 at 08:47 +0200, Marc Haber wrote: > On Tue, Oct 04, 2016 at 08:26:53PM +0100, Sam Morris wrote: > > > > BTW, I noticed the newly-shipped cron job. According to sd_booted(3), > > you should test whether systemd was used to boot the system by running > > [ -d /run/systemd/system

Bug#789690: atop process ends up in cron.service's cgroup

On Tue, Oct 04, 2016 at 08:26:53PM +0100, Sam Morris wrote: > BTW, I noticed the newly-shipped cron job. According to sd_booted(3), > you should test whether systemd was used to boot the system by running > [ -d /run/systemd/system ] rather than examining /proc/1/exe. This is a > stable interface

Bug#789690: atop process ends up in cron.service's cgroup

On Tue, 2016-10-04 at 08:09 +0200, Marc Haber wrote: > tags #789690 unreproducible moreinfo > thanks > > Hi Sam, > > I do not see this behavior any more in the atop from experimental. > Are > you in a position to try this version? > > I would like to mark this bug as "fixed in experimental" and

Bug#789690: atop process ends up in cron.service's cgroup

tags #789690 unreproducible moreinfo thanks Hi Sam, I do not see this behavior any more in the atop from experimental. Are you in a position to try this version? I would like to mark this bug as "fixed in experimental" and will do so unless you have said that the experimental version still has

Bug#789690: atop process ends up in cron.service's cgroup

> Sam Morris > But more annoyingly, restarting cron results in atop being killed! This was another bug, that even got fixed in stable: cron (3.0pl1-127+deb8u1) jessie; urgency=medium . * d/cron.service: Use KillMode=process to kill only the daemon. The default of

Bug#789690: atop process ends up in cron.service's cgroup

Package: atop Version: 1.26-2 Severity: normal I guess this is due to logrotate running 'invoke-rc.d atop _cron'. $ systemctl status atop cron ● atop.service - LSB: Monitor for system resources and process activity Loaded: loaded (/etc/init.d/atop) Active: active (exited)