> > Sure enough, after creating the directory cron now works. > Neat script. > Thanks! (Shouldn't the installation have created the > directory, though?) >
This diagnostic script came about because there are a number of environmental elements that have to be in place before cron can run. Although they are created, these elements can get deleted. Attached below is version 1.6 of the script. The update in this version adds a message recommending that the user examine cron's log file. ------------------------------------------- cron_diagnose.sh will attempt to diagnose problems with cron. It will not modify any files on your computer. You might need to run the script several times. Each time that it finds a problem, it stops and displays a descriptive message. Please read the messages that the script generates, especially if it reports no errors, but you still cannot get cron to work for you. These messages should help you to report problems that occur in setting up cron, and possibly reduce the number of messages about cron that need to be sent to the mailing list. Please report the version number that this script reports so that improvements can be made to it.
cron_diagnose.sh
Description: cron_diagnose.sh
-- 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/