Here's a chin scratcher...
I created the following Cron entry:
0,30 * * * * /home/patrick/ip_update_files/ip_update_
It is intended to be run as root, and as the name of the program suggest it updates IP addresses.
My problem isn't that it doesn't run properly (it has, well for days now), my problem is it kicked out two entries today to my mailbox. one at 11:33 am, and another thirty minutes later. There is the normal log entry that was written by the cron command, and as a little 'wrinkle' the program itself prints a time stamp on the log whenever it is run as well. NOTHING in the log suggests the program was ever run at these odd times, but it does suggest that it was run normally at the 11:30, 12:00 times...
Why in the world would cause this behaviour?
I created the following Cron entry:
0,30 * * * * /home/patrick/ip_update_files/ip_update_
It is intended to be run as root, and as the name of the program suggest it updates IP addresses.
My problem isn't that it doesn't run properly (it has, well for days now), my problem is it kicked out two entries today to my mailbox. one at 11:33 am, and another thirty minutes later. There is the normal log entry that was written by the cron command, and as a little 'wrinkle' the program itself prints a time stamp on the log whenever it is run as well. NOTHING in the log suggests the program was ever run at these odd times, but it does suggest that it was run normally at the 11:30, 12:00 times...
Why in the world would cause this behaviour?
