This is the mail archive of the
mailing list for the Cygwin project.
cron requires COLD BOOT
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Subject: cron requires COLD BOOT
- From: "Soukup, Kevin (IL50)" <kevin dot soukup at honeywell dot com>
- Date: Tue, 28 Aug 2001 10:13:25 -0500
I've checked the FAQ, the user guides and the documentation and I've
searched the mail archive relentlessly. I've tried variations of the scripts
and configurations of cron with no luck. I hope I've satisfied the
expectation that try to figure this out on my own.
I am stumped.
I'm running CygWin on an NT 4.0 sp5 Intel workstation. I've installed the
cron service as follows:
cygrunsrv -I cron -p /usr/sbin/cron.exe -a -D -e "CYGWIN=tty ntsec"
The cron job is installed as follows:
30 10 * * * /home/kdsoukup/cadlib_admin/crontest/bart_nightly >>
The cron service runs. Cron starts my script as desired. When I run the cron
command line on a bash command line, it executes everything great. When cron
attempts to start the same job, it gets through most of the script but locks
up just about everything up on my workstation. The command set never
completes and the only way out of it is to COLD BOOT the workstation. There
are a total of about 4 sh.exe processes running by the time I have to
Any suggestions would be greatly appreciated. If you'd like to see the
script I'm executing (calls executables, cat, sed, awk, blah, blah, blah)
please reply directly and I'll provide it to you.
Thanks much and best regards,
Kevin Soukup Sensing and Control
CAD/CAM Engineer 11 W. Spring St
Oracle DBA Freeport, IL 61032
(815) 235-6944 Office
(815) 235-5959 Fax
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html