This bug was fixed in the package cron - 3.0pl1-116ubuntu1 --------------- cron (3.0pl1-116ubuntu1) natty; urgency=low
* Merge from debian unstable (LP: #696953), remaining changes: - debian/control: + Requires debhelper >= 7.3.15ubuntu2 (for Upstart). + Move MTA,lockfile-progs to Suggests field. - debian/cron.upstart: Add Upstart script. - debian/{prerm,postinst,postrm}: + Don't call update-rc.d,invoke-rc.d and /etc/init.d/cron. - debian/rules: Call dh_installinit to install Upstart job properly. cron (3.0pl1-116) unstable; urgency=high * Upload with approval from Release Team to get RC bug fixes in Squeeze (see http://lists.debian.org/debian-release/2010/12/msg00719.html) * do_command.c, popen.c: - Use fork() instead of vfork(). * do_command.c: - Close an unused stream in the fork()ed child prior to exec'ing the user's command, thereby avoiding an fd leak. Closes: #604181, LP: #665912 Previously to this, in conjunction with LVM, the fd leak may have the effect of the user being spammed by warnings every time a cron job was executed. * crontab.5: - Fixed the example demonstrating how to run a job on a certain weekday of the month (date range was off-by-one). Also, the same example contained a superfluous escape, resulting in wrong output. Closes: #606325 * cron.init: - Added $named to Should-Start, in case @reboot jobs need DNS resolution. Closes: #602903 - Added nslcd to Should-Start. LP: #27520 -- Lorenzo De Liso <bla...@ubuntu.com> Mon, 03 Jan 2011 20:32:01 +0100 ** Changed in: cron (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665912 Title: Fix for #151231 leaves tmpfile fd open in actual job -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs