This is the mail archive of the
cygwin
mailing list for the Cygwin project.
cron and mail: a stupid question (please don't kill me)
- From: "Julio Emanuel" <costaju at gmail dot com>
- To: "Cygwin Mailing list" <cygwin at cygwin dot com>
- Date: Mon, 21 Jul 2008 18:11:51 +0100
- Subject: cron and mail: a stupid question (please don't kill me)
- References: <af075b00807210917s424b5400u414fc4c422d28843@mail.gmail.com>
Hi all,
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??
I don't have any experience with the "mailing subsystem" of unix /
cygwin worlds, so I'm quite lost here.
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??!)
So, I began fiddling with ssmtp (which seemed to me like the most
simple and direct thing to use, since I don't want any real mail on my
host)... but all I achieved was some mails sent to our real mail relay
with some unknown addresses (it tried with some domain account which
doesn't have email).
SO... for the question: Is it possible to do a) and b), as layed out
above, without to mess with mails and such? How?
___________
Julio Costa
--
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/