You are not logged in.
I've tried all these methods but can't understand why only "_COMM" works.
[root@alarmpi ~]# journalctl -u crond
-- Logs begin at Sat 2014-07-05 14:49:30 WEST, end at Sat 2014-07-05 15:01:02 WEST. --
[root@alarmpi ~]# journalctl -u crond.service
-- Logs begin at Sat 2014-07-05 14:49:30 WEST, end at Sat 2014-07-05 15:01:02 WEST. --
[root@alarmpi ~]# journalctl _EXE=crond
-- Logs begin at Sat 2014-07-05 14:49:30 WEST, end at Sat 2014-07-05 15:01:02 WEST. --
[root@alarmpi ~]# journalctl _COMM=crond
-- Logs begin at Sat 2014-07-05 14:49:30 WEST, end at Sat 2014-07-05 15:01:02 WEST. --
Jul 05 14:50:01 alarmpi crond[287]: pam_unix(crond:session): session opened for user tigre by (uid=0)
Jul 05 14:50:01 alarmpi CROND[287]: pam_unix(crond:session): session closed for user tigre
Jul 05 15:00:01 alarmpi crond[418]: pam_unix(crond:session): session opened for user tigre by (uid=0)
Isn't "crond.service" a systemd unit? Isn't _EXE an alias for _COMM?
I'm a bit lost.
Last edited by tigrezno (2014-07-05 20:17:08)
Offline
I don't know about archlinux ARM, but in Archlinux, our cron package is cronie, and the service is actually cronie.service.
Offline
I don't know about archlinux ARM, but in Archlinux, our cron package is cronie, and the service is actually cronie.service.
that was the problem! I was using crond because that's what I saw in the process list.
Thank you!
Offline