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
** Branch linked: lp:debian/sid/cron
--
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
The difference is that your example redirects both stdout and stderr
while mine only redirected stdout.
Anyway, your test shows the problem too: 5 - /tmp/tmpfznXN8E
shouldn't be there. There's a close missing somewhere in the child.
--
Fix for #151231 leaves tmpfile fd open in actual job
Yes, my bad there.
Anyway, I'm pretty sure I found the issue. However, it appears as though
the author of the original patch had attempted this too (without
success), and left a warning in there cautioning against this. It
appears as if the problem was only an implementation issue, but given
the
(I added that patch, which was provided by Justin Pryzby, to cron)
Strange. On my Debian Squeeze system with cron-115 (diff to -114 is only
in packaging), I get the following results with the test case you
provided:
$ cat /tmp/stdout.log
normal
total 0
dr-x-- 2 chris chris 0 Oct 24 23:43 .
