On 3 July 2012 02:39, Christoph Anton Mitterer <cales...@scientia.net> wrote: > On Tue, 2012-07-03 at 02:04 +0200, Javier Fernández-Sanguino Peña wrote: >> This should be >> fixed in cron itself (through it's SIG handler) > Are you going to follow this up?
I you are asking if this is going to fix in the current cron version the answer is no. Since the latest cron release (4.1) and the cron fork (cronie) already do this properly the approach would be to upgrade our current cron version to the latest upstream. I'd rather not include yet another patch in our sources, working on moving over to 4.1 is preferred. Regards Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
