On 09/09/2020 09:38, Ralph Corderoy wrote:
> Hi Patrick,
>
>> Is it intentional that OnCalender= has a different spelling of
>> Calend[a,e]r than OnCalendar=20:12?
> Nope! Thanks, that fixes it.
>
> $ systemctl cat updatedb.timer
> # /usr/lib/systemd/system/updatedb.timer
> [Unit]
> Description=Daily locate database update
>
> [Timer]
> OnCalendar=daily
> AccuracySec=12h
> Persistent=true
>
> # /etc/systemd/system/updatedb.timer.d/override.conf
> [Timer]
> OnCalendar=
> OnCalendar=20:12
> Persistent=no
> $
> $ systemctl show updatedb.timer | grep OnCalendar=
> TimersCalendar={ OnCalendar=*-*-* 20:12:00 ;
> next_elapse=Wed 2020-09-09 20:12:00 BST }
> $
>
> Now I just have to work out why updatedb.conf(5)'s PRUNE_BIND_MOUNTS
> doesn't seem to have an effect. :-)
>
Seems like it might be slightly related, so has anyone experienced cron
jobs sporadically (kind of randomly) not running when they're meant to?On the same pi as has the kernel OOPS issue, I have cron jobs to turn the power and SD access lights off at night and on at day, and run an update script in the early morning. For a while now, these don't always seem to run. I haven't bothered to dive into exactly why, but I was wondering if there were any common misconfigurations that cause this. I wouldn't find myself especially surprised if the kernel OOPS was also somehow knocking CRON out/off-kilter. Hamish
signature.asc
Description: OpenPGP digital signature
-- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
