[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

crons scripts should report status info in the mail

Since the output from cron jobs is mailed anyhow, as it should be, I
think that all cron scripts should report in as they are run, and that
this should be made a standard.  Here's why.

Every morning, lately, after my cron.daily directory is run, I get
this in the mail:

tar: Removing leading / from absolute path names in the archive
tar: Cannot add file /etc/securetty: No such file or directory
tar: Removing leading / from absolute path names in the archive
shell-init: could not get current directory: getcwd: cannot access parent directories

`The `tar` errors about stripping / are no big deal; I will
2>/dev/null them.  I don't know why it cannot find
"/etc/securetty"... anyone know?  The reason I want the scripts to
report is so I can find out which one gives that 'shell-init' error.

I've gone and added an `echo $0` to each script.  Tomorrow morning
I'll know which script it is. :-)

Q: Is anyone using `autoconf`?  I wonder if it's worth learning to
use, and what people use it for.  (I've barely glanced over the
manuals for it, so far.)

Karl M. Hegbloom <karlheg@inetarena.com>
Portland, OR  USA
Debian GNU 1.2  Linux 2.1.36 AMD K5 PR-133

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: