On 11/22/2010 09:34 AM, Jaap Winius wrote: > Quoting Christian Kastner <deb...@kvr.at>: > >> If you're interested and/or willing to help testing, an amd64 package >> (and source package, for other platforms) based on the current -115 plus >> the (one-line) fix for this issue are available here: >> >> http://www.kvr.at/debian/pool/main/c/cron/cron_3.0pl1-116_amd64.deb >> http://www.kvr.at/debian/pool/main/c/cron/cron_3.0pl1-116.dsc > > Can do!
Great, thanks for testing! > I've successfully compiled it and installed the 32-bit version > on three systems. However, during the install process, I did get this > warning: > > insserv: warning: current stop runlevel(s) (1) of script `cron' \ > overwrites defaults (empty). > > In contrast, I installed the pre-compiled amd64 version on one very new > system and did not receive this error. It seems to be a minor problem, > though. This has been reported as #583714. insserv issues a warning because the default runlevels changed between Lenny and Squeeze (which is why you don't see it on the new system); you can safely ignore this (or follow the steps outlined in #583714). > Regarding the main issue, before the patched cron version was applied, > all four systems suffered from the file descriptor leak. After it was > applied, the problem was solved in all four cases. Success! Do you have any jobs that generate output and mail it? If yes, please monitor and see if anything weird happens -- specifically, if you don't get any output mailed at all. The current fix /should/ be OK, but it isn't 100% clean, and therefore I hesitate to push it yet. I'll see that I get around to validating it or implementing a better fix RSN. Christian
signature.asc
Description: OpenPGP digital signature
