[EMAIL PROTECTED] wrote: >> 5. Redirect all of the output to /dev/null, and forget about it. You >> should have a way to check that your scripts ran w/o checking your >> email, so the email is just clutter. If you discover a problem, >> you can rerun the job and look at the output. > > Now I'm confused. You don't always rely on > /etc/cron.daily script emails? What other reliable way > is there to reliably/continually get updates? > > I got cron scripts doing remote backups and such. What > is more convenient/safe to keep tabs on the operations > than an email report? >
This same concept has come up in installfest questions. There is no guaranteed delivery in email, so if you really need a reliable monitoring/notification operation, you have to use use a protocol specifically designed for the job (Tracy: jump in anytime). I suppose you could add a home-grown protocol layer on top of email, by adding automated confirmations and retries, or simply ensuring that email gets sent whether there's an exception or a normal report, and then it's the receiving end that has to detect a missing email receipt. ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
