Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: CRON problems
Date: Fri, 7 May 2004 11:12:41 -0400
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E01459888@ex02.co.idirect.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Harig, Mark" <maharig AT idirect DOT net>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i47FE21r010797

> 
> Two places to look for the actual error are /var/log/cron.log and the
> Windows event log.  Perhaps Mark can add this to the output of his
> script...
> 	Igor
> -- 

I assume that what you are suggesting is that some
text pointing the user to /var/log/cron.log be added,
not actually displaying the log file.  Is this correct?

I am hesitant to display the contents of the log
file because it adds to the text displayed, and there
have been a number of problems reported simply
because users do not read the output of the
script carefully.  In addition, the log can get
long.

---

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