X-Spam-Check-By: sourceware.org
Message-ID: <5abc24640704110541i4c3e1a36m7fc00300203394b2@mail.gmail.com>
Date: Wed, 11 Apr 2007 08:41:53 -0400
From: "Andrew Louie" <louiea AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: cron 4.1-1
In-Reply-To: <announce.3.0.1.32.20070411064934.00ba6708@incoming.verizon.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <announce DOT 3 DOT 0 DOT 1 DOT 32 DOT 20070411064934 DOT 00ba6708 AT incoming DOT verizon DOT net>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 4/11/07, Pierre A. Humblet  wrote:
> I have updated cron to version 4.1

>
> If /usr/sbin/sendmail does not point to a mailer, the cron postinstall script
> links it to the (new) script /usr/bin/cronlog.


Thanks! It took me a week to figure out how to set up up cron
correctly! first you had to learn how to setup logging correctly just
for the chance that you might catch some kind of useful error message,
then you had to setup an e-mailer correctly, and if you didn't cron
wouldn't tell you that, it would just stop the command after some
random amount of time has passed. >_<

>
> /usr/bin/cronlog is a "poor man's mailer" that writes cron output (if any)
> to HOME/cron.log.  HOME can be superseded in the crontab file.
> The temporary output of /usr/bin/cronlog is written to /tmp/cron.XXX.log and
> /tmp/cron.XXX.log.err. These files are deleted if all goes well but can
> provide useful debugging information if HOME/cron.log cannot be written
> (e.g. on some network drives).
> /usr/bin/cronlog can be edited to suit particular needs.
>
but, can't we put all the logs in the same place like /var/log by default?
You probably have a good reason to stick it in HOME, I just thought
I'd put the question out there.

--
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/