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 will do > so unless you have said that the experimental version still has the > issue by the end of October 2016 > > Greetings > Marc >
Hi Marc, I'm not able to try this on a system running jessie right now
but having looked at the changes in the package I'm sure that the bug
will be fixed by the systemd units included in that version--thanks!
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 that will not change in the future. You can also test
the exit status of 'systemd-notify --booted'.
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. For example, see /etc/cron.daily/apt-compat
and apt-daily.{timer,service}.
Regards,
--
Sam Morris <https://robots.org.uk/>
PGP: rsa4096/CAAA AA1A CA69 A83A
892B 1855 D20B 4202 5CDA 27B9
signature.asc
Description: This is a digitally signed message part
