Ye, cron-config is the way to go. I used on my last install and thanks to Pierre, it solved my problem. Another point I would like to make here is that Igor needs to be a bit more kind in his reply. It doesn't help if you make people feel stupid. Not everyone is an EXPERT like you. Anyway thanks Pierre for your help and contributions.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pierre A. Humblet Sent: Wednesday, July 27, 2005 10:09 AM To: cygwin@cygwin.com Subject: Re: Cron problems with cygwin... Igor Pechtchanski wrote: > Third, please run the cron_diagnose.sh script and examine the results. > If it's a simple permission issue, that script should catch it. cron_diagnose.sh was not designed for Win2003 and is not a good diagnostic tool there. It won't catch all permissions issues and may raise false alarms. As far as I know, all the tests performed by cron_diagnose.sh are included in cron-config. We should stop pointing to cron_diagnose.sh, except possibly in a case (I have not seen one yet) where cron-config does not produce a working cron environment. If that happens, it would be helpful to report precisely what was wrong and how it had to be fixed. Pierre -- 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/ -- 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/
