group.of.nepali.translators team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

This is fixed in Debian with the following change:

cron (3.0pl1-128) unstable; urgency=medium

  * d/cron.service: Use KillMode=process to kill only the daemon.
    The default of KillMode=control-group kills all the processes in the control group, for example when restarting the daemon. This is a deviation from past behavior we do not want. Thanks, Alexandre Detiste! Closes: #783683


** Bug watch added: Debian Bug tracker #783683
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783683

** Also affects: cron (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783683
   Importance: Unknown
       Status: Unknown

** Changed in: cron (Ubuntu)
       Status: Confirmed => Triaged

** Also affects: cron (Ubuntu Xenial)
   Importance: Medium
       Status: Triaged

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1527348

Title:
  restarting cron kills children on 16.04 - did not kill on 14.04

Status in cron package in Ubuntu:
  Triaged
Status in cron source package in Xenial:
  Triaged
Status in cron package in Debian:
  Unknown

Bug description:
  In the middle of a script run by cron, I'm restarting the cron service
  (service cron restart).

  The script finishes just fine on 14.04 (and keeps doing whatever is
  after the cron restart). On 16.04, it kills the script meaning that it
  kills all its children.

  Behavior should be reverted where children are not killed upon
  restart.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1527348/+subscriptions