* Michael Schwendt <[EMAIL PROTECTED]> [2003-08-28 10:20]: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 28 Aug 2003 05:46:25 -0400, Juan Martinez wrote: > > > > I can see that now! It has been running every minute, and filling my > > > mailbox with notices! How do I get rid of the notification function? > > > > > > MAILTO= didn't work. > > > > Redirect the output to /dev/null Cron uses /bin/sh as its shell so your > > redirection would look like this "fetchmail >&/dev/null" That redirects > > stdout as well as stderr to /dev/null. Read the man page for bash and > > look for REDIRECTION for an explanation. > > That way you would lose any error output from fetchmail which is most > likely not what you would like. Instead, run fetchmail in daemon mode > triggered from a cron job. That is, create a cron job that starts > fetchmail in daemon mode once a day or several times a day to make > sure that after a reboot your user's fetchmail daemon will be started > again. For that cron job, feel free to redirect stdout/stderr to > /dev/null. In daemon mode, fetchmail submits notification messages > about major errors such as ongoing connection failures.
Actually, after playing around with the cron job approach, I went ahead and installed the first replier's startup script, because I boot up my computer several times a day sometimes (sometimes only once), but always at different times, and the first thing I have to do when I boot up is read my mail, so if my bootup time didn't coincide with the time set in the cron job, I would have to start fetchmail manually anyway. The startup script works beautifully, and I have fetchmail running as a daemon through the fetchmailrc file. Thanks for all the help, though. -- Marc Adler -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
