<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 09/22/2014 12:07 PM, Reindl Harald
wrote:<br>
</div>
<blockquote cite="mid:5420110D.5030407@thelounge.net" type="cite">
<pre wrap="">
Am 22.09.2014 um 13:45 schrieb Jóhann B. Guðmundsson:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>On 09/22/2014 11:40 AM, Reindl Harald wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">>> </span>Am 22.09.2014 um 13:28 schrieb Jóhann B. Guðmundsson:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">>>> </span>On 09/22/2014 09:23 AM, Reindl Harald wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">>>>> </span>Am 22.09.2014 um 01:48 schrieb Jóhann B. Guðmundsson:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">>>>>> </span>The reason for increased log entries in the journal is that more things
<span class="moz-txt-citetags">>>>>> </span>are happening now since this is what happening when a job is run.
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>>>> </span>that don't change the fact that a user not acting as
<span class="moz-txt-citetags">>>>> </span>systemd-developer and not debugging his system don't
<span class="moz-txt-citetags">>>>> </span>need that flood
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>>> </span>I guess we have different meaning of message flood
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">>> </span>again: we talk about rsyslog, like it or not
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">> </span>
<span class="moz-txt-citetags">> </span>Then file a bug report against rsyslog and provide a patch which fixes
<span class="moz-txt-citetags">> </span>the default log filtering in Fedora to your expectation but leave
<span class="moz-txt-citetags">> </span>systemd out of it.
</pre>
</blockquote>
<pre wrap="">wow - in any other case the systemd developers saying that
they don't workround things because problems has to be
solved at the root-cause - practice what you preach and
make the log-verbosility configureable!</pre>
</blockquote>
<br>
Serves no purpose whatsoever doing that. <br>
<br>
<blockquote cite="mid:5420110D.5030407@thelounge.net" type="cite">
<pre wrap="">
* rsyslog is <b class="moz-txt-star"><span class="moz-txt-tag">*</span>not<span class="moz-txt-tag">*</span></b> responsible for the message flood produced by systemd</pre>
</blockquote>
<br>
No but it is responsible for the filtering <-- of log messages.<br>
<br>
<blockquote cite="mid:5420110D.5030407@thelounge.net" type="cite">
<pre wrap="">
* systemd is the one producing it without prefixes
</pre>
</blockquote>
<br>
This is simply untrue as "journalctl -o export" will show you.<br>
<br>
I suggest you stop blaming systemd for your own administrative
incompetence and broken implementation of rsyslog and syslog-ng in
Fedora ( I tried to get it fixed before we defaulted to journal YES
IT WAS BROKEN BEFORE AND STILL IS but was not allowed to do so thank
those Red Hatters in the governing body's of Fedora ( FESCO/FPC )
for it's brokeness ) and write an rsyslog template suited for your
environment which will filter things to your liking and expectation
or better yet complain to those FESCO/FPC members since they need to
learn a hard lesson of accepting responsibility for their own
actions in the distribution. <br>
<br>
You can find how to write an rsyslog template in the upstream
rsyslog documentation using it's powerful filtering capabilities and
by looking at for example the one spice-vdagentd
/etc/rsyslog.d/spice-vdagentd.conf in Fedora.<br>
<br>
JBG<br>
</body>
</html>