X-Spam-Check-By: sourceware.org Date: Wed, 11 Apr 2007 09:43:53 -0400 From: "Pierre A. Humblet" Subject: Re: [ANNOUNCEMENT] Updated: cron 4.1-1 To: "Andrew Louie" , Message-id: <00f701c77c3f$729045b0$3c0110ac@wirelessworld.airvananet.com> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 6.00.2900.2869 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit References: <5abc24640704110541i4c3e1a36m7fc00300203394b2 AT mail DOT gmail DOT com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com ----- Original Message ----- From: "Andrew Louie" To: Sent: Wednesday, April 11, 2007 8:41 AM Subject: Re: [ANNOUNCEMENT] Updated: cron 4.1-1 | > | > /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. I thought HOME was more likely to be writable by a random user. For now I would like to keep it that way and accumulate some feedback. It's also easy to customize. For example currently cronlog only saves the last output, some people may want to save everything. To make it more flexible there could be environment variables in the crontab to tell cronlog what to save and where to save it. But I prefer to start simple. Pierre -- 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/