Control: severity -1 critical Re: Joerg Morbitzer 2015-04-29 <[email protected]> > In the past (with Squeeze, Wheezy etc.) cron was always daemonized > and that behaviour never(!) happened, I think this -f is a pretty > dangerous thing.
The problem isn't running in the foreground, but systemd's process group handling. Re: Alexandre Detiste 2015-05-01 <2522456.jJ8AmF7lJg@antec> > Control: severity -1 important > > > Hi, > > To solve your problem, you can add "KillMode=process" > into the [Service] stanza of cron.service. > > I guess this is an important bug that should be solved in Debian 8.1 > due soon. The behavior was different for decades, and this change isn't mentioned in NEWS.Debian to make the user aware. I guess everyone who has been managing cron as a sysadmin will get bitten badly by this change. I'd strongly opt to change the KillMode as mentioned above. #debian-devel seems to agree, so I'm upgrading this bug to RC. (critical as it's killing "random" processes) > http://www.freedesktop.org/software/systemd/man/systemd.kill.html > > | If set to control-group, all remaining processes in the control group of > this unit will be killed on unit stop > | If set to process, only the main process itself is killed. > | Defaults to control-group. > > Other distro's do that too > > https://git.fedorahosted.org/cgit/cronie.git/tree/contrib/cronie.systemd > http://arch-general.archlinux.narkive.com/FcUpb8Nw/protect-a-cron-job-from-systemd > > (not Debian) > http://anonscm.debian.org/cgit/pkg-cron/pkg-cron.git/tree/debian/cron.service Christoph -- [email protected] | http://www.df7cb.de/
signature.asc
Description: Digital signature
