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
>>>> 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
>> 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
> 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
Otherwise, it would appear to me that logging should be a bit more
specific... (either specific to frameworks or applications). I mean, are
there any other toolkits (like Qt) shipping their own rsyslog.d snippets ?
dunno - i just don't want to get my global syslog flooded becasue every
piece of software starts to just blow their informational output to
journald and i am tired to write rsyslog-snippets and logrotate-snippets
everytime another piece of software starts to do so by hand on each and