<br><br><div class="gmail_quote">2011/3/21 Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com">awilliam@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Mon, 2011-03-21 at 15:08 -0400, Genes MailLists wrote:<br> ><br>
> Understood - although I thought the point being bandied about here was<br>
> not the offending rsyslog itself - but rather that it brought to light a<br>
> new sensitivity - of what appears to be systemd issue. Unless I missed<br>
> it and systemd now has a -4 karma ...<br>
<br>
</div>That's the perspective being bandied about on this list, yes, but<br>
it's...ahem...not necessarily clear-cut. The immediate issue here is<br>
clearly the rsyslog/selinux bug. The question of whether systemd should<br>
try to cope more gracefully with syslog being entirely broken is a quite<br>
separate one.<br>
<div class="im"><br></div></blockquote><div>excuse me sir, but this thread _is_ about systemd :)</div><div>also, my experience is that systemd was also affected by some mdmonitor issue ....</div></div>