X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=4.3 required=5.0 	tests=AWL,BAYES_00,BOTNET,SPF_NEUTRAL
X-Spam-Check-By: sourceware.org
Message-id: <01c901c9c2a5$d07ec0d0$940410ac@wirelessworld.airvananet.com>
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
To: "Ting Zhou" <tzhou AT guardiananalytics DOT com>, <cygwin AT cygwin DOT com>
References: <1255DA8CFF890A44B8F034ADB81D1A6031B1A274D2 AT guardianmx DOT guardian DOT lan>
Subject: Re: cron does not do anything
Date: Tue, 21 Apr 2009 13:22:53 -0400
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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


----- Original Message ----- 
From: "Ting Zhou" <>
To: <cygwin AT cygwin DOT com>


I'd like to report a bug with Vixie cron. I have cygwin installed with cron option. And I ran 
"cron-config" and set up everything. Cron-diagnose script didn't find any problem. Cron service 
was also started without problem. However, cron just wouldn't run the simple command I set up in 
the crontab "/usr/bin/touch /tmp/abcd".
****************
Hi,

On your system you have syslog running, instead of using the Windows event log.
That's fine, except that your syslog configuration now controls how the cron log messages
are handled. The current "cronbug" script is not smart enough to figure that out
and does not provide enough info to help you (everything looks normal to me)

Please send us in attachment the file containing the cron logs (if they are kept).
If it's very long, use "fgrep -i cron" to isolate relevant lines.
Alternatively, stop both syslog and cron, then restart cron only, run the cronbug script
again and send us the output.

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/