Hi Eliot,
Actually, Bobsie provided them, I just reiterated them.
I'm not sure about this, but I think with my server at least, this format only sends email if there are problems while running the cron job. The log file is saved regardless and is deleted when the next cron event is run. For my database of ~2,500 links, the log file is only 40k or so, which is a minimal amount of disk space.
I don't see that there's much harm to doing both. Besides, it was the tech support from my host that recommended adding the email notification to stay on top of any problems, as "any number of things can go wrong with crontab while unattended."
Dan
Quote:
Using the codes that Dan providedActually, Bobsie provided them, I just reiterated them.
Quote:
This is only necessary if you want both a log file created and an email sent to verify that the job has been completed.I'm not sure about this, but I think with my server at least, this format only sends email if there are problems while running the cron job. The log file is saved regardless and is deleted when the next cron event is run. For my database of ~2,500 links, the log file is only 40k or so, which is a minimal amount of disk space.
I don't see that there's much harm to doing both. Besides, it was the tech support from my host that recommended adding the email notification to stay on top of any problems, as "any number of things can go wrong with crontab while unattended."
Dan
