On Mon, Jul 02, 2012 at 11:04:43PM +0200, Michael Stapelberg wrote: > Quoting Marc Haber (2012-07-02 22:53:09) > > systemd needs to restart atop daily at midnight, the log rotation > > mechanism depends on that. > > > > Please take a close look at how init script and daily cron job work > > together. > I did. Why would this not work with systemd? logrotate will stop atop, > rotate the log file and start it again, just like with the init script. > Why would systemd be involved in that at all?
the cron job calls the init script. Is this really the intended way to interact with systemd? How is it made sure that the new atop process is placed into the correct cgroup, how is a systemd-induced restart of systemd inhibited? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
