[merge request] Please sync 'cron' from Debian main

Bug #1541302 reported by dino99
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cron (Debian)
Fix Released
Undecided
Unassigned
cron (Ubuntu)
Fix Released
Critical
Unassigned
Nominated for Xenial by Alberto Salvia Novella

Bug Description

xenial still have an outdated version; please sync it from:
http://metadata.ftp-master.debian.org/changelogs/main/c/cron/cron_3.0pl1-128_changelog

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

 -- Christian Kastner <email address hidden> Sun, 03 May 2015 15:25:18 +0200

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cron 3.0pl1-127ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Feb 3 11:24:01 2016
SourcePackage: cron
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
dino99 (9d9) wrote :
description: updated
dino99 (9d9)
tags: added: upgrade-software-version
Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

See also bug 1527348 (restarting cron kills children on 16.04 - did not kill on 14.04) bug-status=yet unconfirmed

summary: - Please sync from Debian main
+ [merge request] Please sync 'cron' from Debian main
Changed in cron (Ubuntu):
status: New → Confirmed
Changed in cron (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

Would say, with best intentions this is a duplicate of bug 1527348.

Revision history for this message
dino99 (9d9) wrote :

The Debian report should be closed (as per its #52 post) but post #57 point some side effects (no more comments during the last 6 months)

Source: cron
Source-Version: 3.0pl1-127+deb8u1

We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive.

... so #1527348 seems useless now.

Revision history for this message
dino99 (9d9) wrote :

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

 -- Christian Kastner <email address hidden> Sun, 03 May 2015 15:25:18 +0200

Changed in cron (Debian):
importance: Unknown → Undecided
status: Unknown → New
status: New → Fix Released
Changed in cron (Ubuntu):
status: Confirmed → In Progress
status: In Progress → Triaged
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Since cron 3.0pl1-128ubuntu2 is available in Ubuntu 16.04, I believe this issue can be marked resolved.

Changed in cron (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.