On Wed, Aug 31, 2011 at 01:58:01PM +0100, Richard W.M. Jones wrote: > On Wed, Aug 31, 2011 at 02:21:19PM +0200, Lennart Poettering wrote: > > On Wed, 31.08.11 12:43, Kalev Lember (kalevlember@xxxxxxxxx) wrote: > > > It's the job of PID 1 to reap zombies without a parent. My guess would > > > be that systemd is in a frozen state and not doing that. > > > > > > Could it be https://bugzilla.redhat.com/show_bug.cgi?id=732020 that's > > > causing systemd to abort? > > > > That would be my guess too. > > > > Richard, please upgrade to systemd 34-1! > > After a reboot it so far hasn't happened (systemd 33-1 from F16). > > I would suspect the kernel 3.0.0-1 was to blame, since that had a > known bug with locking (RHBZ#722472). systemd had a problem where it would crash on "systemctl enable". Better upgrade to 34-1. -- Tomasz Torcz RIP is irrevelant. Spoofing is futile. xmpp: zdzichubg@xxxxxxxxx Your routes will be aggreggated. -- Alex Yuriev -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
