[systemd-devel] How to quiet cron sessions logging with systemd-212?

[Reindl Harald]

Am 09.06.2014 17:28, schrieb Leonid Isaev:
> On Mon, Jun 09, 2014 at 10:48:31AM +0300, Leho Kraav wrote:
>> Date: Mon, 09 Jun 2014 10:48:31 +0300
>> From: Leho Kraav <leho at kraav.com>
>> To: Reindl Harald <h.reindl at thelounge.net>,
>>  systemd-devel at lists.freedesktop.org
>> Subject: Re: [systemd-devel] How to quiet cron sessions logging with
>>  systemd-212?
>> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
>>  Thunderbird/24.5.0
>>
>> On 09.06.2014 10:43, Reindl Harald wrote:
>>> nobody cares because the developers point of view is that what is
>>> interesting for them needs to be also faced by the sysadmin
>>>
>>> otherwise this would be only logged in debug-mode and bugreports
>>> not closed: https://bugzilla.redhat.com/show_bug.cgi?id=1072368#c3
>>>
>>> frankly if that messages would at least have a prefix or a different
>>> process than systemd one could filter them out with rsyslog.conf
>>> without supress relevant boot messages
>>
>> Thanks for the info. I tried googling for this relatively hard, couldn't
>> find that bug.
>>
>> Language on that bug is probably counterproductive, but other than that,
>> some reasonably sensible way should exist to simply stop logging crap, not
>> relying on just output filtering.
> 
> What you see are authpriv-level logs, so it would be a really bad idea to
> suppress them, regardless of their source

no user needs them, there are already logs which command was
started for which user from crond with just 3 lines

Jun  9 19:01:01 rawhide CROND[1696]: (root) CMD (run-parts /etc/cron.hourly)
Jun  9 19:01:01 rawhide run-parts[1696]: (/etc/cron.hourly) starting 0anacron
Jun  9 19:01:01 rawhide run-parts[1705]: (/etc/cron.hourly) finished 0anacron
Jun  9 20:01:01 rawhide CROND[1735]: (root) CMD (run-parts /etc/cron.hourly)
Jun  9 20:01:01 rawhide run-parts[1735]: (/etc/cron.hourly) starting 0anacron
Jun  9 20:01:01 rawhide run-parts[1744]: (/etc/cron.hourly) finished 0anacron

they are introduced in that floody way with recent systemd

all the decades before crond did run fine, logs exactly what
you need to know if /var/log/secure and /var/log/crond
without writing *hundret thousands* loglines all day long
on machines with a lot of cronjobs


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140609/b5f8c7d8/attachment.sig>