On Sat, 27 Jun 1998, Anthony E. Greene wrote:
->Because if you schedule some thing to occur later, you may not besitting
->there to see the messages. You may not even be logged in. Your monitor may
->not be on at the scheduled time. Cron could have been desiged to write a
->log for you to review later or it could have been designed to email the
->results of the command. I don't think email was a bad design choice.
*** Hi Tony,
Sounds obvious now but - like I mailed to Vidiot - the man cron & crontab
aren't really exploding with info so understanding the above is not the
first thing that happens. In the light of this new information I must also
admit that the e-mail isn't such a bad choice. Leaves me still with my
major problem. Just in case you want to mail me some more feedback on
solving it, check the mail I send to Paul concerning my suprise of not
finding /usr/sbin/crontab to exist and crontab -e writing the crontab
entries to /tmp/...
Zoki.
Mailed with Linux and Pine.
%% Fin de message / End of message %%
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
