Crons via the plugin directory not working

[joelones]

Simply trying to port over all my crons from the go file to /boot/config/plugins/ and it simply won't have it. This shouldn't be too complicated but yet..

 

From what I understood:

 

Created a dir under plugins:

/boot/config/plugins/cronjobs

 

Slapped a test cron file with .cron extension, call it : test.cron

* * * * * /usr/bin/touch /tmp/test_cron_ok &> /dev/null

 

root@Tower:/boot/config/plugins/cronjobs# ls -al
drwxrwxrwx  2 root root 4096 Feb 19 09:35 ./
drwxrwxrwx 21 root root 4096 Feb 19 08:56 ../
-rwxrwxrwx  1 root root   49 Feb 19 09:38 test.cron*

Then ran update_cron and don't see anything in /etc/cron.d/root and it would appear that the cron job didn't run as well.

 

Thoughts ?

[Squid]

Its actually because of how safemode is handled.

 

unRaid won't process a .cron file unless the plugin referred to in /boot/config/plugins/cronjobs is installed (in this case, cronjobs is the plugin)

 

Pop your .cron files into /boot/config/plugins/dynamix and you'll be good.  Or alternatively, schedule your scripts with the user scripts plugin

[joelones]

1 hour ago, Squid said:

Its actually because of how safemode is handled.

 

unRaid won't process a .cron file unless the plugin referred to in /boot/config/plugins/cronjobs is installed (in this case, cronjobs is the plugin)

 

Pop your .cron files into /boot/config/plugins/dynamix and you'll be good.  Or alternatively, schedule your scripts with the user scripts plugin

 

Thanks, it appears to run now. Does the running of the job get put in any log for debug purpose?

[Squid]

4 hours ago, joelones said:

Does the running of the job get put in any log for debug purpose?

Only if you have logging within your job