X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	Yes, hits=6.6 required=5.0 tests=BAYES_50,BOTNET,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
Message-id:	<00de01cb4544$ec2520e0$2a0010ac@wirelessworld.airvananet.com>
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
To:	"Blaine Miller" <bmiller AT coastside DOT net>, <cygwin AT cygwin DOT com>
References:	<4C769D88 DOT 5060905 AT coastside DOT net>
Subject:	Re: Will cron runnnnig as a service cause the server to lock up?
Date:	Thu, 26 Aug 2010 13:34:22 -0400
MIME-version:	1.0
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: "Blaine Miller" 
To: <cygwin>
Sent: Thursday, August 26, 2010 12:59


| I'm running cron as a service. Twice this week this server has died and 
| needed cold rebooting to get the system back.
| 
| Questions - First, will cron as a service on a Windows 2003 R2, standard 
| system cause this sort of behavior?

This has never been reported, as far as I know.
You run cron as yourself, if I remember correctly. This avoids various setuid
issues. Except for that, cron is a plain vanilla program. 

|                 Second, if it does, how do I run cron to keep it from 
| doing this?
| 
| A snippet of the errors I'm getting are:
| 
| cron: unknown option -- D
| usage: /usr/sbin/cron [-n] [-x [ext,sch,proc,pars,load,misc,test,bit]]
| 

Where does the -D come from?
That used to be an option in cron 3. It is now replaced by -n
Without -n, cron will not remain under the control of cygrunsrv.

| My crontable is:
| 
| $ crontab -l
| # DO NOT EDIT THIS FILE - edit the master and reinstall.
| # (/tmp/crontab.yRr11boUdm installed on Thu Aug 19 14:17:23 2010)
| # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie 
| Exp $)
| 00 05 * * * /cygdrive/c/scripts/xfer_vvm_mysql.sh
| 00 05 * * * /cygdrive/c/scripts/xfer_vvm_ora.sh
| 00 05 * * * /cygdrive/c/scripts/xfer_nab_vnnab.sh
| 00 10 * * * /cygdrive/c/scripts/xfer_nab_csnab.sh
| 00 06 * * * /cygdrive/c/scripts/xfer_dellsrv20.sh
| 00 06 * * * /cygdrive/c/scripts/xfer_directory.sh
| 00 06 * * * /cygdrive/c/scripts/xfer_perforce.sh
| 00 06 * * 2 /cygdrive/c/scripts/xfer_fileserv.sh
| 
| 
| As you can see, I'm not passing any paramets to the cron daemon...

Remember that PATH may not be the same under cron as under 
interactive bash. So "find" and other tools may use a Windows version.
But that doesn't explain a crash.

Pierre


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -