Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: problem of cron in cygwin xp, final solution! Date: Wed, 1 Oct 2003 12:29:53 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Harig, Mark" To: "Andrew DeFaria" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h91GURxY008349 > > Maybe such things should be added to Mark Harig's "cron_diagnose.sh"? > > > To make the life easier for the other followers: > > 1. Need to set the mode of cygwin1.dll > > > > $ chmod +x /bin/cygwin1.dll This is a more general problem than a problem with cron's many files. A sanity check for cygwin might be desirable, but I do not know all of the many files and conditions that would need to be checked for this. Often, when all else fails, the solution is to uninstall cygwin and re-install it. > > 2. Need to create another directory $ mkdir /etc/cron.d > > Also make it accessible, by changing the permission. The absence of this directory is already checked for, as are the directory permissions. If it is missing, then the script notifies the user and halts. > > 3. Then, follow the standard guideline to start cron service, as > > $ cygrunsrv --stop cron > > $ cygrunsrv --remove cron > > $ cygrunsrv --install cron -p /usr/sbin/cron -a -D > > $ cygrunsrv --start cron > > The user is notified about these commands by 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/