Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Wed, 27 Jul 2005 10:08:55 -0400
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject: Re: Cron problems with cygwin...
To: <cygwin AT cygwin DOT com>
Reply-to: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Message-id: <180101c592b4$ba0d2780$3e0010ac@wirelessworld.airvananet.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit

Igor Pechtchanski wrote:

> Third, please run the cron_diagnose.sh script and examine the results.
> If it's a simple permission issue, that script should catch it.

cron_diagnose.sh was not designed for Win2003 and is not a good
diagnostic tool there. It won't catch all permissions issues and may raise
false alarms.
As far as I know, all the tests performed by cron_diagnose.sh are
included in cron-config. 
We should stop pointing to cron_diagnose.sh, except possibly in a
case (I have not seen one yet) where cron-config does not produce
a working cron environment. If that happens, it would be helpful to
report precisely what was wrong and how it had to be fixed.

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/