[systemd-devel] I wonder… why systemd provokes this amount of polarity and resistance

Reindl Harald h.reindl at thelounge.net
Mon Sep 22 12:58:46 UTC 2014


Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
>>> > Then file a bug report against rsyslog and provide a patch which fixes 
>>> > the default log filtering in Fedora to your expectation but leave 
>>> > systemd out of it.
>> 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!
> 
> Serves no purpose whatsoever doing that.
>>
>> * rsyslog is *not* responsible for the message flood produced by systemd
> 
> No but it is responsible for the filtering <-- of log messages.
> 
>> * systemd is the one producing it without prefixes

it is ridiculous to have the need of filtering

> This is simply untrue as "journalctl -o export" will show you.

where is it in the message?
the process is "systemd"

how to distinct between user sessions and systemn boot?
":programname" don't work and ":msg, startswith" don't work

Mar 18 23:01:01 rawhide systemd[577]: Stopped target Default.
Mar 18 23:01:01 rawhide systemd[577]: Stopping Basic System.
Mar 18 23:01:01 rawhide systemd[577]: Stopped target Basic System.
Mar 18 23:01:01 rawhide systemd[577]: Stopping Paths.
...................

> I suggest you stop blaming systemd for your own administrative incompetence 

i suggest you get rid of that arrogance and some other developers
too because it's the reason for the subject and proves that you
*do not* care about users as long you have not the same opinion

you are the one demanding a friendly tone from me, well, than
practice what you preach or stop whining if someone calls you
names the next time

who do you think you are to assess others 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) 

just don't create messages the majority of users don't want and need
to see until debugging and even systemd needs to realize that the
world is not turning around it

> 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

who do you think you are?

that arrogance and pure ignorance is the reason for subject and
related websites as well as for users from time to time not
complaining as nice as you would like it

hence fedora devel CC'ed
__________________________________________________________________________

here the relevant links you decided to strip out and replace
with your arrogant abuse as you always do if someone has a
differnt opinion but demand from others not act the same way

here you have a simple calculation
https://bugzilla.redhat.com/show_bug.cgi?id=1072368#c8

why don't you look at https://bugzilla.redhat.com/show_bug.cgi?id=1072368
and the workaround "loginctl enable-linger" leads to another bugreport
open for months: https://bugzilla.redhat.com/show_bug.cgi?id=1088619#c54

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140922/1f2a85b4/attachment.sig>


More information about the devel mailing list