On Tue, Nov 08, 2011 at 12:16:41PM +0100, Santiago Garcia Mantinan wrote: > Do you need any other info to help solve this bug?
Sorry for the slow reply, I was traveling. I am currently a bit lost what might cause this TBH. I tried to reproduce this in a clean VM and have apache upgraded from from 2.2.16-6+squeeze3 to 2.2.16-6+squeeze4 (just like in your example), it also upgaded libpam and openssl. This worked here, no defunct process. However I ran it by hand, not from cron.daily. I wonder if there is anything else missing to make this reproducable, is there anything special on your apache setup or anything else that might help me to reproduce the issue? > I really think that having the upgrades block daily cron jobs on a stable > machine is something that should not happen, thus I think we should try to > get this solved asap. Yes, this is definitely a critical bug in my book too, I just need some more clues (or a way to reproduce) to figure out how to fix it :/ Cheers, Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
