[Techtalk] Howto remove everything email-related from Debian?
Conor Daly
conor.daly-linuxchix at cod.homelinux.org
Fri Sep 28 10:02:48 UTC 2007
On Fri, Sep 28, 2007 at 11:46:05AM +0200 or so it is rumoured hereabouts,
Michelle Konzack thought:
> Am 2007-09-27 17:43:12, schrieb Conor Daly:
> > It strikes me that cron is at fault here. If a program being run by cron
> > generates output for the screen that is not handled, cron will email that
> > output to the user. The usual way to deal with that is to redirect the
> > output from the program to either a logfile or to /dev/null (if you don't
> > care about the output). Given that unexpected output from a program
> > running under cron is usually an error message, it's probably better to
> > use a logfile rather than /dev/null . My cron entries look like:
> >
> > * * * * * /path/to/program1 > /path/to/logfile 2>&1
> > * * * * * /path/to/program2 > /dev/null 2>&1
> > * * * * * /path/to/program3 >> /path/to/appended/logfile 2>&1
> >
> > These will eliminate cron's attempts to email stuff.
>
> Why not set:
>
> MAILTO=
>
> in the crontab? -- This avoid mangeling of all crontab-lines
>
What happens if there's output to deal with? Does cron just dump it?
Conor
--
Conor Daly <conor.daly at cod.homelinux.org>
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/G/S/O d+(-) s:+ a+ C++(+) UL++++ US++ P>++ L+++>++++ E--- W++ !N
PS+ PE Y+ PGP? tv(-) b+++(+) G e+++(*) h-- r+++ z++++
------END GEEK CODE BLOCK------
http://www.geekcode.com/ http://www.ebb.org/ungeek/
More information about the Techtalk
mailing list