On Sun, May 09, 2010 at 07:29:46AM -0400, Haines Brown KB1GRM ET1 wrote: > > <http://www.cyberciti.biz/faq/disable-the-mail-alert-by-crontab-command/#more-229> > > > > p...@rick > > Thanks, Patrick, but the reason for my writing is that this approach > (using the command "fetchmail > /dev/null 2>&1" did not work.
Cron will only generate e-mail if the program has output, which the above command guarantees won't happen. One can only conclude that if you're still getting e-mail, you somehow did it wrong. I can only think of two possibilities: either you have a typo in your crontab, or you updated your crontab improperly (perhaps by editing the file in the spool directory directly?). Well, I suppose it's possible that there's a bug in your version of cron also... but that seems extremely unlikely. I assume you are running it in cron via your own (i.e. not root) user? If so, then running "crontab -l" will print out what your crontab looks like. You might post the output of that to the list, so we can have a look. Running as a daemon will certainly prevent the mail, and filtering with procmail will just as easily make sure you don't see it. I will mention that I formerly ran fetchmail as a daemon, and then ran into some problem (the details of which I've forgotten, it was quite a while ago) which prompted me to switch to running it from cron. I invoke it as above, and as expected I don't get any e-mail. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgpXomlPS55Zr.pgp
Description: PGP signature
