Will cron runnnnig as a service cause the server to lock up?

[Blaine Miller]

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?
                 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]]


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

???

Thanks for your time and assistance...

Blaine



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