From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms-smtp-05.texas.rr.com ([24.93.47.44] helo=ms-smtp-05-eri0.texas.rr.com) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1C3pSc-0004H4-00 for ; Sun, 05 Sep 2004 01:21:06 -0400 Received: from tomass (cs24328-50.austin.rr.com [24.243.28.50]) by ms-smtp-05-eri0.texas.rr.com (8.12.10/8.12.7) with ESMTP id i855L4Bu010470 for ; Sun, 5 Sep 2004 00:21:04 -0500 (CDT) Received: from stivers_t by tomass with local (Exim 4.34) id 1C3pSZ-0007IT-U0 for speakup@braille.uwo.ca; Sun, 05 Sep 2004 00:21:03 -0500 Date: Sun, 5 Sep 2004 00:21:03 -0500 To: speakup@braille.uwo.ca Message-ID: <20040905052103.GD13462@tomass.dyndns.org> Mail-Followup-To: speakup@braille.uwo.ca References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: X-Request-PGP: http://tomass.dyndns.org/~stivers_t/pubkey.asc X-Uptime: 1 week 1 day 22 hours 14 minutes 49 seconds User-Agent: Mutt/1.5.6+20040818i From: Thomas Stivers X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: cron question X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2004 05:21:06 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Sep 04 2004 at 10:11:09PM -0400, Scott Howell wrote: > Folks, > > I've setup a cron job for my wife that polls for her mail. The problem > is that cron sends her a message everytime fetchmail is run. I have a > similar setup, but I don't get these messages unless something is wrong > with my setup, but doesn't appear to be the case. She is getting mail, > but just tuns of these messages from Cron. > I know there is a way to stop these messages bening sent to her, but I > can't think of what that is. Has anyone a suggestion? One suggestion is to redirect the stdout and stderr of your call to fetchmail in the crontab to /dev/null. Something like fetchmail 2>&1 >/dev/null would do the trick. Another IMHO better suggestion is to have fetchmail run as a daemon polling for mail at regular intervals. You can set up a /etc/fetchmailrc to get any mail you need and put it in any user's mailbox. I think that the Debian version of fetchmail automatically starts as a daemon when you have a /etc/fetchmailrc. This automatic starting only takes place at boot time however so you would need to run "/etc/init.d/fetchmail start" and you should be set. The fetchmail man page has all the details on fetchmailrc files and they are pretty easy to set up. HTH - -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan Thomas Stivers e-mail: stivers_t@tomass.dyndns.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBOqI/5JK61UXLur0RAqbKAJsHnR/o0B5kWW/TLVDQ/l0r0AX7IACfYeI4 XA5xz75JuSLMA7MKzpXAhRE= =TmS1 -----END PGP SIGNATURE-----