Mail Archives: cygwin/2008/07/21/13:31:58
Julio Emanuel wrote:
> I've searched a bit already, and have been through the cron, ssmtp,
> and crontab manpages. Still, there is something that I don't quite
> understand: why on earth the cron job's output are put in e-mails??
cron was written with the intention of being able to run jobs for normal
users, not just sysadmins. How else is it supposed to notify a user
that a job it ran on that users behalf completed with errors? Users
might not have access to the system logs and even if they did they
almost certainly wouldn't know or think to check them. But on a
traditional unix system every user does have a local mail spool file and
users are accustomed to reading email, so it's a pretty natural fit.
But cron itself really doesn't know anything about email per se, it just
knows that when the job outputs to stderr, it pipes that output to a
"/usr/sbin/sendmail", whatever that is. That is typically a symlink to
something that sends mail but it doesn't have to be.
> All I want to do is:
> a) have some jobs running unnatended and scheduled; (apparently done,
> whith some simple tests)
> b) have the output of this jobs LOGGED, preferably on syslog, with
> some identification of the process who generated it; (don't have a
> clue??!)
Did you read /usr/share/doc/Cygwin/cron-*.README? It explains cronlog
which if symlinked as sendmail will log the output.
Alternatively, you can do whatever you want with your job's output by
redirecting or piping stdout and/or stderr to a location or program of
your choice directly in the crontab entry. There's nothing that says
you need to let cron handle it. You can use 'logger' if you want that
location to be the syslog.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -