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

["Jóhann B. Guðmundsson"]

On 09/21/2014 11:09 PM, Reindl Harald wrote:
> Am 22.09.2014 um 00:48 schrieb Jóhann B. Guðmundsson:
>> On 09/21/2014 10:23 PM, Reindl Harald wrote:
>>> Am 22.09.2014 um 00:15 schrieb Jóhann B. Guðmundsson:
>>>>> Now alot of the resistance and polarity that is taking place like in the url you pointed at is hiding itself
>>>> behind
>>>>> their misinterpretation of the so called "Unix philosophy" and claiming that we somehow fall short on the
>>>>> guidelines originates from few things Doug McIlroy,Rob Pike,Ken Thompson said sometime in the 70's or rather the
>>>>> "Unix philosophy" was implied not by what these individuals said but rather by what they did which more or less
>>>>> boils down to this..
>>>>> 11. When a program has nothing surprising to say, it should say nothing
>>> then flood logs with nothing relevant should not happen
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1072368
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1053315
>> ?
>>
>> I dont see the connection here systemd is informing you what start/stopped when these cron job ran
> with *that many* lines?

The reason for increased log entries in the journal is that more things 
are happening now since this is what happening when a job is run.

>
> that information already exists in /var/log/secure and /var/log/cron
> these lines are completly useless for a non-developer

Irrelevant to us what is stored in text files so that needs to be 
handled downstream.

>
> consider that not refuse that often what a user wants to
> see or not to see *as default* because as developer you
> have other needs is one of the reasons *endusers* get
> sometimes really angry

Depends on personal preference and practices

Cron users already are divided into two religious notification groups.

Those that have cron job that send email that notifies every time that 
it ran ( to know it ran ) and those that do not send an email unless the 
job it was running failed and rely on logwatch to inform them if the 
cron job ran or not.

>
>> If you dont like it filter it and retrieve only the information you want/need with journalctl
> if they would have a prefix i would filter them to nowhere in rsyslog
>
> please understand that not everybody is using journalctl

Well this is upstream that ships nothing but journalctl whether they use 
it or not.

JBG