On Tue, 10.06.14 20:05, Leho Kraav (l...@kraav.com) wrote: > > On 09.06.2014 09:33, Leho Kraav wrote: > >After upgrading systemd 208 -> 212, every single cron job creates this > >flood in systemd journal: > > > >juuni 09 09:20:01 xps14 crond[15112]: pam_unix(crond:session): session > >opened for user root by (uid=0) > >juuni 09 09:20:01 xps14 systemd[15113]: pam_unix(systemd-user:session): > >session opened for user root by (uid=0) > >juuni 09 09:20:01 xps14 systemd[1]: Starting user-0.slice. > > ... > >juuni 09 09:20:02 xps14 systemd[1]: Started User Manager for UID 0. > >juuni 09 09:20:02 xps14 CROND[15116]: (root) CMD (test -x > >/usr/sbin/run-crons && /usr/sbin/run-crons ) > >juuni 09 09:20:02 xps14 CROND[15112]: pam_unix(crond:session): session > >closed for user root > >juuni 09 09:20:02 xps14 systemd[1]: Stopping User Manager for UID 0... > > ... > >juuni 09 09:20:02 xps14 systemd[1]: Stopped User Manager for UID 0. > >juuni 09 09:20:02 xps14 systemd[1]: Stopping user-0.slice. > >juuni 09 09:20:02 xps14 systemd[1]: Removed slice user-0.slice. > > Another related question to trying to filter this output: why some > lines are logged with program "crond" and some "CROND"?
No idea. cron sends that string, we merely display it... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel