Hi Folks,
I enabled email for cron jobs, so I could see failures.
Many of the standard cron jobs create output that is unnecessary.
For example, /var/cache/netmgr/lock_timer.sh
runs once a minute, and includes two calls to curl
without the -s
flag. These then generate an email from cron every time, containing the progress-report output from curl
.
Likewise, the job /sbin/clean_reset_pwd
that runs once a day has errors, and reports:
sh: /sbin/qlicense: No such file or directory
[-1102] = Clean_Reset_Pwd_Over_Endtime;
and there are others.
Standard practice is to collect cron job output and send it to an administrator to detect errors: it seems the developers did not do this.
This is on a TS-664 running the latest OS, 5.2.3.3006