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) since Wed 2015-05-27 23:23:47 BST; 3 weeks 5
days ago
May 27 23:23:46 traxus systemd[1]: Starting LSB: Monitor for system
resources and process activity...
May 27 23:23:47 traxus systemd[1]: Started LSB: Monitor for system
resources and process activity.
● cron.service - Regular background program processing daemon
Loaded: loaded (/lib/systemd/system/cron.service; enabled)
Active: active (running) since Wed 2015-05-27 23:23:46 BST; 3 weeks 5
days ago
Docs: man:cron(8)
Main PID: 264 (cron)
CGroup: /system.slice/cron.service
├─ 264 /usr/sbin/cron -f -L 15
└─5277 /usr/bin/atop -a -w /var/log/atop/atop_20150623 600
The atop unit stays 'active' even though the process has exited (this will
probably always happen while a sysvinit script is used rather than a systemd
unit).
But more annoyingly, restarting cron results in atop being killed!
I don't see why it's necessary to couple the cleanup of old log files to the
startup of the service. It would seem simpler to have two cron jobs; one job to
restart the service (via the regular 'start' verb so that
/lib/lsb/init-functions.d/40-systemd is able to do its job, hence fixing
this bug) and the second job to delete the old log files.
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (550, 'stable-updates'), (550, 'stable'), (520, 'unstable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 libc6 2.19-18
ii libncurses5 5.9+20140913-1+b1
ii libtinfo5 5.9+20140913-1+b1
ii lsb-base 4.1+Debian13+nmu1
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages atop recommends:
ii cron 3.0pl1-127
atop suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
