Only slightly tangential, but the issue of the crazy crontab has come up over the years. Here’s a little insight from one of the past developers: Mult emals - Cron <asterisk@24408486> [ -e /usr/sbin/fwconsole ] && sleep $((RANDOM - #26 by tm1000
I believe the direction was that cron would only be used as a trigger to load FreePBX every minute and fire off any jobs contained in its jobs table.
But – and there may be a technical reason behind this, I don’t know – it does that (fwconsole job) and also runs more cron jobs that… are also FreePBX. (fwconsole backup and fwconsole certificates for example)
Makes no sense to me. And because there’s apparently the risk of a user or some other process corrupting the crontab, it needs to be validated all the time.