Very Computer

Not directly.  But what you _can_ do is write a wrapper script for
all of your cron jobs that does this for you.  At our site, we have
a wrapper called "cron.wrapper" (descriptive, isn't it?) that does
this, via the following arguments:

    cron.wrapper command mail_subject userlist ...

We then put this entry in cron for each job, and the wrapper executes
"command", and if there's output, it sends mail to "userlist" with a
subject of "subject" which describes the job so you can quickly scan
the output.

Cheers,
-+JLS
--
                               \  


http://www.aracnet.com/~seagull   \

  /path/to/some/command 2>&1 | /usr/bin/mailx -s"something descriptive here" geoff

(This is on HP/UX, where mailx is the barebones mailer that allows
specifying a subject.)

The key is that you don't want your cron command to produce any stdout
or stderr. Redirecting stderr to stdout and then piping both to a
mail program does the trick.

Geoff

--
Geoff Allen, WSU School of EE&CS sysadmin support guy.  Finger for PGP key.

___________________________________________________________________________
The Bible tells us to love our neighbors, and also to love our enemies;
probably because generally they are the same people.
               -- G. K. Chesterton

Thanks for any help!  
--
###  John Nolan  


###  Drexel University, Philadelphia         ~      (_)/ (_)