- Minor
Starting with 6.12.4 update_cron is no longer running during system start in a virtualized environment (Unraid VM). This worked until 6.11.5.
Not running update_cron has impact on the User Scripts plugin that relies on that tool to add it's "Custom schedules" to "/etc/cron.d/root". So a scripts with "Custom schedules" attached, no longer runs from within the User Scripts plugin.
One can work around this by calling update_cron manually after system start to add these missing entries in a second step.
Here's a post that describes the problem. Diagnostics attached.
Thanks for listening.
On a barebone server it looks like that. This is missing on a virtualized server. Don't know if this is required to run over and over again for three times:
root@Tower:~# grep -i cron /var/log/syslog Sep 4 10:48:51 Tower crond[1870]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice Sep 4 10:48:59 Tower root: Setting up cron for background notifications *** *** The following lines are missing in a virtualized environment *** Sep 4 10:51:16 Tower emhttpd: shcmd (270): rm -f /boot/config/plugins/dynamix/mover.cron Sep 4 10:51:16 Tower emhttpd: shcmd (271): /usr/local/sbin/update_cron Sep 4 14:35:29 Tower emhttpd: shcmd (219514): rm -f /boot/config/plugins/dynamix/mover.cron Sep 4 14:35:29 Tower emhttpd: shcmd (219515): /usr/local/sbin/update_cron Sep 4 14:35:49 Tower emhttpd: shcmd (219643): rm -f /boot/config/plugins/dynamix/mover.cron Sep 4 14:35:49 Tower emhttpd: shcmd (219644): /usr/local/sbin/update_cron