Normaly the cron job runs quietly in the background, and that’s a good thing.
However, many admins would like to know a little more about the jobs being executed.
cron.php’s own --verbose flag generates a lot of noise, which in some situations includes information that is completely unnecessary. For example, if calendars only need to be updated once a year, those calendar job are called each time cron.php is started (which fills the log files), while the jobs in question are not executed at all.
nc-cron-logger solves this problem by providing its own verbosity levels.
It automatically detects whether APCu is needed and if the memory level is too low and sets those values when calling
It supports file locking so that cron jobs running in parallel don’t interfere with each other. Secure log rotation is also provided and can be installed with the script itself.
The script is completely standalone and requires no internet access. Unlike other ebtb scripts, no modules are downloaded from the internet, as it must be able to run reliably every 5 minutes in every situation.
The file contains the installation instructions:
Restriction: If this wrapper can be applied to Snap or Docker deployments has not been tested.
Much and good luck,
ernolf