Hi,
I've been using FreeBSD 13.0 on an RPI 4 and I noticed something weird when setting up a cron job. I could not get the cron job to run, so I inspected /var/log/cron and found 2 different datetimes. As you can see below, it logs when I edit the crontab using the correct datetime of the system (the same as what
Why would the cron daemon be running +4 hours ahead of the system time? Thanks!
I've been using FreeBSD 13.0 on an RPI 4 and I noticed something weird when setting up a cron job. I could not get the cron job to run, so I inspected /var/log/cron and found 2 different datetimes. As you can see below, it logs when I edit the crontab using the correct datetime of the system (the same as what
date
outputs), then you can also see log entries from /usr/sbin/cron
that are +4 hours ahead of the system datetime. So after seeing that, I added 4 hours to my cron job and it ran as expected. I am using NTP for time since the RPI has no hardware clock, and the timezone is set correctly as EST.Why would the cron daemon be running +4 hours ahead of the system time? Thanks!
Bash:
Jun 6 06:57:00 rpi4-bsd /usr/sbin/cron[11602]: (root) CMD (/root/mtree-specs/mtree-spec-cron-job.sh)
Jun 6 02:57:43 rpi4-bsd crontab[11607]: (root) BEGIN EDIT (root)
Jun 6 02:59:50 rpi4-bsd crontab[11607]: (root) REPLACE (root)
Jun 6 02:59:51 rpi4-bsd crontab[11607]: (root) END EDIT (root)
Jun 6 07:00:00 rpi4-bsd /usr/sbin/cron[1316]: (root) RELOAD (tabs/root)
Jun 6 07:00:00 rpi4-bsd /usr/sbin/cron[11612]: (root) CMD (newsyslog)
Jun 6 07:00:00 rpi4-bsd /usr/sbin/cron[11613]: (operator) CMD (/usr/libexec/save-entropy)
Jun 6 07:00:00 rpi4-bsd /usr/sbin/cron[11614]: (root) CMD (/usr/libexec/atrun)
Jun 6 07:05:00 rpi4-bsd /usr/sbin/cron[11627]: (root) CMD (/usr/libexec/atrun)