X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=4.4 required=5.0 	tests=AWL,BAYES_05,BOTNET,SPF_NEUTRAL
X-Spam-Check-By: sourceware.org
Message-id: <020c01c9c2c3$f71687f0$940410ac@wirelessworld.airvananet.com>
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
To: "Ting Zhou" <tzhou AT guardiananalytics DOT com>
Cc: <cygwin AT cygwin DOT com>
References:  <1255DA8CFF890A44B8F034ADB81D1A6031B1A274D2 AT guardianmx DOT guardian DOT lan>  <01c901c9c2a5$d07ec0d0$940410ac AT wirelessworld DOT airvananet DOT com>  <alpine DOT DEB DOT 1 DOT 00 DOT 0904211324340 DOT 14823 AT pilot DOT trilug DOT org>  <1255DA8CFF890A44B8F034ADB81D1A6031B1A274E2 AT guardianmx DOT guardian DOT lan>
Subject: Re: cron does not do anything
Date: Tue, 21 Apr 2009 16:58:44 -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" <>
Sent: Tuesday, April 21, 2009 1:33 PM


Thanks for the quick response. The crontab line is literally like:

28 19 * * * /usr/bin/touch /tmp/abcd

Pierre, attached is the fgrep result of all the logs in /var/log. "cron.log" was created but is 
empty all along.

Let me know if I can supply further diagnostic information.

******************
Right, cron does nothing. But ...
The job is supposed to run at 19:28 every day
You started cron at 19:26:30, it's not clear if the crontab existed then.
You edited the crontab at 19:27:19
When 19:28 came, cron reloaded the crontab but did not run anything.
I don't know if it's by design or not, you are playing it close.
Have you tried using * * * * * in the crontab while you are debugging this?

Also try running a command like "env" that produces an output.
It should appear in ~/cron.log or in /tmp/cronXXXX if there is a problem.

Finally your group is mkgroup-l-d. This suggests that /etc/group
may not be up to date.

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/