If you build good log files (at least updated when in doubt of what your cron is doing), you are going to know exactly what is not working. You could even add a perl script to the crontab that would check the results of your log files and email you about any trouble.
Reading some lines of your log files, it is easier to know what is not working, the rest is just guessing.
| { | \ | ( | ' | v | ' | ) | / | } | ||||||||||||||||||||||||||||||
| ( | \ | _ | / | ) | _ | _ | _ | _ | ` | ( | ) | ' | _ | _ | _ | _ | ||||||||||||||||||||||
| ( | = | ( | ^ | Y | ^ | ) | = | ( | _ | _ | ^ | ^ | ^ | ^ | ||||||||||||||||||||||||
| _ | _ | _ | _ | \ | _ | ( | m | _ | _ | _ | m | ) | _ | _ | _ | _ | _ | _ | _ | _ | _ | ) | c | h | i | a | n | o | , | a | l | b | e | r | t | o |
In reply to Re: cron script best practices
by chanio
in thread cron script best practices
by jimbus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |