Am 29.02.2016 um 19:50 schrieb Rex Dieter:
> Reindl Harald wrote:
>>
>> Am 29.02.2016 um 19:43 schrieb Rex Dieter:
>>> Reindl Harald wrote:
>>>
>>>> Am 29.02.2016 um 19:29 schrieb Rex Dieter:
>>>>> Reindl Harald wrote:
>>>>>
>>>>>> Am 29.02.2016 um 18:42 schrieb Rex Dieter:
>>>>>>> qt5-qtbase has build options:
>>>>>>>
>>>>>>> + -no-journald ........ Do not send logging output to
>>>>>>> journald.
>>>>>>> -journald ........... Send logging output to
journald.
>>>>>>>
>>>>>>> and I'm considering enabling the -journald option for
f24, and
>>>>>>> concerns or objections?
>>>>>>
>>>>>> please ship some rsyslog.d/ snippet with it to not clutter
>>>>>> /var/log/messages for people which continue to use rsyslog for a
lot
>>>>>> of reasons
>>>>>
>>>>> I'm unfamiliar with that, can you be more specific with how that
>>>>> works
>>>>> and is related to journald usage, and ideally, provide a specific
>>>>> snippet to use
>>>>
>>>> something like below and see also
>>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1304828
>>>>
>>>> it's annoying on a rsyslog-setup that you get everything in the
global
>>>> logfile (/var/log/messages) which makes it hard to recognize important
>>>
>>>
>>> Sorry if I'm missing something, but what does what you're suggesting
>>> have
>>> to do with journald ?
>>
>> whatever you blow to journald ends in /var/log/messages when rsyslog is
>> running until there are rules to put it in specific logfiles - that's it
>
> both system *and* user journal entries land in /var/log/messages ? If
> so,
> that's interesting... and a bit unfortunate.
how should rsyslog distinct between them?
you already get /var/log/messages flooded with "kscreen" messages wehn
login via "sddm" to a kde-session as example
perfect example how careless logging makes the admin simply bling
because he no longer is able to find interesting records between all the
noise