[systemd-devel] How to reduce systemd logging to syslog ?

[Lennart Poettering]

On Mon, 21.07.14 16:18, Mantas Mikulėnas (grawity at gmail.com) wrote:

> On Mon, Jul 21, 2014 at 1:41 AM,  <surfer at emailengine.net> wrote:
> >                 2014-07-20T00:15:01.978142-07:00 core systemd[1]: Starting Session 2 of user root.
> >                 2014-07-20T00:15:01.979526-07:00 core systemd[1]: Started Session 2 of user root.
> >                 2014-07-20T00:30:01.065850-07:00 core systemd[1]: Starting Session 3 of user root.
> >                 2014-07-20T00:30:01.067825-07:00 core systemd[1]: Started Session 3 of user root.
> >                 2014-07-20T00:45:01.155187-07:00 core systemd[1]: Starting Session 4 of user root.
> >                 2014-07-20T00:45:01.182571-07:00 core systemd[1]: Started Session 4 of user root.
> 
> Looks like something – perhaps a cron daemon – opens a logind session
> every 15 minutes. But if I remember correctly, background jobs are not
> meant to do that at all? It might be that the log spam is caused by
> misconfigured /etc/pam.d/cron or something such...

Well, cron jobs should open proper PAM sessions when this is about
running normal users' jobs. But I am really shure it shouldn't bother if
this about system user's jobs. PAM sessions are primarily something to
set the environment for unpriviliged user code, but system users are
different there...

Lennart

-- 
Lennart Poettering, Red Hat