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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.1.0.6.0.20040702134345.033af4d0@pop.prospeed.net>
X-Sender: 
Date: Fri, 02 Jul 2004 13:44:31 -0400
To: william DOT b DOT parsons AT us DOT westinghouse DOT com, cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Trouble starting cron (solved)
In-Reply-To: <slrnceb6b8.k2.wbparsons@l1409613.ct.wec.com>
References: <slrnceb20i DOT ak DOT wbparsons AT l1409613 DOT ct DOT wec DOT com> <Pine DOT GSO DOT 4 DOT 58 DOT 0407021244500 DOT 22362 AT slinky DOT cs DOT nyu DOT edu> <slrnceb6b8 DOT k2 DOT wbparsons AT l1409613 DOT ct DOT wec DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:21 PM 7/2/2004, you wrote:
>Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu> wrote:
>> On Fri, 2 Jul 2004, Will Parsons wrote:
>> 
>>> I am trying to get cron working and am having difficulties.  I installed
>>> the following minimal crontab:
>>>
>>> $ crontab -l
>>> # DO NOT EDIT THIS FILE - edit the master and reinstall.
>>> # (crontab.wbp installed on Tue Jun 29 07:47:31 2004)
>>> # (Cron version -- $Id: crontab.c,v 1.7 2003/04/15 15:13:41 corinna Exp $)
>>> 0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/date >> /tmp/date.log
>>>
>>> And installed cron using:
>>>
>>> $ cygrunsrv -I cron -p /usr/sbin/cron -a -D
>>>
>>> Trying to start:
>>>
>>> $ cygrunsrv -S cron
>>> /usr/bin/cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
>>> The service has not been started.
>>>
>>> /var/log/cron shows:
>>   ^^^^^^^^^^^^^
>> This should be /var/log/cron.log, right?
>
>Right.
>
>> 
>>> [569] cron started
>> 
>> A couple of other things to try -- look in the Windows Event log, and run
>> the cron_diagnose.sh script (search the archives).  FWIW, your mounts look
>> fine, so I'd suspect a permission problem of some sort.
>>   Igor
>
>The Event log showed nothing, but running the script resulted in:
>
>  cron_diagnose.sh 1.2
>
>  Your computer does not appear to have a /etc/cron.d directory.
>  Please investigate this problem, and run this script again.
>
>Sure enough, after creating the directory cron now works.  Neat script.
>Thanks!  (Shouldn't the installation have created the directory, though?)


Yes.  The postinstall script will do it if it can (and if it runs).


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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