Package: at
Version: 3.1.12-1
Severity: wishlist
I have a proposal. Due to the _massive_ pain in the neck for the user to
figure out what the heck went wrong with his at job if something went
wrong, why not send mail:
Your at job (Number... submitted on:... run at:... that was in
atjob filename...) exited with a nonzero exit value.
Here is what it printed (stdout and stderr): ...
And here was the source of the at job you submitted: ...
Else, the user must check if he has a backup of the atspool, and he must
figure out what filename it was, etc. (Take failed at job number from
current message, printf %x jobnumber, then look for that in the
filenames in his backup.)
Which is almost the same as asking him to dig out a backup of a mail
message (but even harder)... when instead the mail system already sends
him the text of any failed mail, so at should too... unless he say,
gives a flag: at --dont-send-source-on-failure.
You might say that cron doesn't send such mail... but one need only do
crontab -l to see the source.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
