Excellent! Thank you all for the quick answers. I had no idea that fetchmail could run as a daemon. That is definitely the best way to do it, as I don't want to have multiple crontab entries (to run it every five minutes), and I don't want to disable other error mailings from cron (via MAILTO env var for cron).
-Percival On Thu, Mar 23, 2000 at 04:46:39PM -0500, Ben Collins wrote: > On Thu, Mar 23, 2000 at 11:49:09AM -0800, Percival wrote: > > I am looking for some help with cron. I have read the man pages, but I > > still cannot figure out how to schedule a job and NOT have the stdout > > emailed to me. > > > > I am trying to run fetchmail to check some remote e-mail boxes several > > times an hour, and it works very well, but I end up with TOO many e-mails > > from cron. I tried to redirect, but I think that fetchmail doesn't work > > like that. > > > > Is there a better way to do this? Can exim do this for me? > > Well for one if you want to make fetchmail do regular email checks, run it > like this: > > fetchmail -d 300 > > This will make it run in the background and check for email every 5 > minutes (600 seconds). But, to answer your question, you really need to > redirect the output like so: > > ...... fetchamil >/dev/null 2>&1 > > This sends all of stdout to /dev/null, and redirects stderr to stdout > (basically sending it to /dev/null too). You may want to leave off the > "2>&1" part so that error messages still get email to you, but for your > situtation, I suggest running fetchmail with -d from the command line. > > -- > -----------=======-=-======-=========-----------=====------------=-=------ > / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ > ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' > `---=========------=======-------------=-=-----=-===-======-------=--=---' > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
