X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By:	sourceware.org
Date:	Tue, 21 Apr 2009 13:25:39 -0400 (EDT)
From:	William Sutton <william AT trilug DOT org>
To:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
cc:	Ting Zhou <tzhou AT guardiananalytics DOT com>, cygwin AT cygwin DOT com
Subject:	Re: cron does not do anything
In-Reply-To:	<01c901c9c2a5$d07ec0d0$940410ac@wirelessworld.airvananet.com>
Message-ID:	<alpine.DEB.1.00.0904211324340.14823@pilot.trilug.org>
References:	<1255DA8CFF890A44B8F034ADB81D1A6031B1A274D2 AT guardianmx DOT guardian DOT lan> <01c901c9c2a5$d07ec0d0$940410ac AT wirelessworld DOT airvananet DOT com>
User-Agent:	Alpine 1.00 (DEB 882 2007-12-20)
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Did you check that your cron job line is formatted correctly?  If your 
line is literally of the form

/usr/bin/touch /tmp/abcd

then it definitely won't run because it is incorrectly written.

William Sutton

On Tue, 21 Apr 2009, Pierre A. Humblet wrote:

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

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

- Raw text -