Re: optimizing systemd, was: f15 no longer starts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





2011/3/21 Adam Williamson <awilliam@xxxxxxxxxx>
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 ....
-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux