optimizing systemd, was: f15 no longer starts

cornel panceac cpanceac at gmail.com
Tue Mar 22 05:37:16 UTC 2011

2011/3/21 Adam Williamson <awilliam at redhat.com>

> On Mon, 2011-03-21 at 15:08 -0400, Genes MailLists wrote:
>  >
> >   Understood - although I thought the point being bandied about here was
> > not the offending rsyslog itself - but rather that it brought to light a
> > new sensitivity - of what appears to be systemd issue. Unless I missed
> > it and systemd now has a -4 karma ...
> That's the perspective being bandied about on this list, yes, but
> it's...ahem...not necessarily clear-cut. The immediate issue here is
> clearly the rsyslog/selinux bug. The question of whether systemd should
> try to cope more gracefully with syslog being entirely broken is a quite
> separate one.
> excuse me sir, but this thread _is_ about systemd :)
also, my experience is that systemd was also affected by some mdmonitor
issue ....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/test/attachments/20110322/cb68d8e2/attachment.html 

More information about the test mailing list