X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=3.0 required=5.0 	tests=AWL,BAYES_20,BOTNET,SPF_NEUTRAL
X-Spam-Check-By: sourceware.org
Message-id: <030b01c9e921$b6c339d0$cb00a8c0@wirelessworld.airvananet.com>
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
To: "sam naqvi" <email_amn AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References: <906740 DOT 60422 DOT qm AT web62504 DOT mail DOT re1 DOT yahoo DOT com>
Subject: Re: Cron jobs stopped working : can't lock cron.pid .. Resouce  temporarily unavailable
Date: Tue, 09 Jun 2009 12:45:34 -0400
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


----- Original Message ----- 
From: "sam naqvi" <>
To: <cygwin AT cygwin DOT com>
Sent: Tuesday, June 09, 2009 11:48 AM


|i had setup some cron jobs on cygwin last Friday. a few of them were test scripts to see if the
cron is firing smoothly on the right time without errors. And there were some actual scripts
too.
| It was working fine on Friday, giving output to all the test scripts at correct times.
|
| however, it did not work for the jobs that it had to run over the weekend. in fact, now, it
does not even run the test scripts.
|
| an error that i could locate in var/log/Cygwin\ cron.log  file is as follows:
| /usr/sbin/cron: can't lock /var/run/cron.pid, otherpid may be 9556: Resource temporarily
unavailable
| please see the attachment for details.
|
| i have gone through the cygwin mail archives and general google search on any similar reported
problem. this problem looks similar (http://www.cygwin.com/ml/cygwin/2008-05/msg00280.html) but
i could not understand what is causing a lock in my case and how to fix it. i am a beginner in
cygwin crons and could not find the problem or the cause of it. can someone please help here?

****************
You are running the cron daemon as SYSTEM on a Windows 2003 Enterprise Server.
On such a system the demon cannot change user context (setuid), thus the jobs don't run.

According to the log, you started using SYSTEM on May 12 but on May 13 you were able to
successfully run the daemon under a user named EXSAN. However on Jun 5 at 20:34:54
you reverted to using SYSTEM.... All of that is clearly visible in the cronbug.txt file you
sent us.

The message "can't lock /var/run/cron.pid" probably indicates that you are trying to start
a new cron while one is already running.

Looks like you are not using cron-config to configure and start the daemon.

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/