in reply to Sanity check: Tiny wrapper script for /bin/mail

Assuming that CRON_macscanner behaves POSIXly, would something like the following not do what you want? ... 
05 12 * * * root /home/atlas/tools/CRON_macscanner >/tmp/CRON_macscann
+er 2>&1 || mail -s "[Nettverk][Error] CRON_macscanner" email@address.
+here < /tmp/CRON_macscanner

[download]
As per usual, just a thought :-)

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^2: Sanity check: Tiny wrapper script for /bin/mail
by FloydATC (Deacon) on Nov 30, 2013 at 11:25 UTC

    I don't think a single one of those cron scripts return proper exit codes since they were originally meant to produce text output if problems were detected and otherwise just be quiet. But if they did then I suppose this solution would work. As a bonus, this approach would leave traces in /tmp which could be useful for summarizing. Hmm.

    -- FloydATC

    Time flies when you don't know what you're doing

[reply]
      In which case, this might be slightly more effective... 
      05 12 * * * root /home/atlas/tools/CRON_macscanner >/tmp/CRON_macscann
+er 2>&1; test -s /tmp/CRON_macscanner && mail -s "[Nettverk][Error] C
+RON_macscanner" email@address.here < /tmp/CRON_macscanner

      [download]

      Be very wary of leaving/using traces in /tmp - on most OS'es, this gets emptied at shutdown &/or startup. If you definitely want records, then I'd suggest creating & using a subdirectory of /var/log.

      A user level that continues to overstate my experience :-))
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom