Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.0.1.1.0.20031221155817.03755a50@127.0.0.1>
X-Sender: 
Date: Sun, 21 Dec 2003 16:04:05 -0500
To: David Bath <davidbath AT newsguy DOT com>, Cygwin List <cygwin AT cygwin DOT com>
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Cron problem after using hibernate
In-Reply-To: <3FE606A3.3050904@newsguy.com>
References: <3FE4B029 DOT 4080104 AT newsguy DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20031221144602 DOT 0374ca50 AT 127 DOT 0 DOT 0 DOT 1> <3FE606A3 DOT 3050904 AT newsguy DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 03:46 PM 12/21/2003, David Bath you wrote:
>Larry Hall wrote:
>>At 03:25 PM 12/20/2003, David Bath you wrote:
>>
>>>I have been running cron for over a year now without any problems until recently. Typically I leave my PC running XP on all day and then hibernate it very late in the evening, turning it back on each morning. Cron would run without fail executing as expected until sometime after 11/21. Around that time I used setup to update all out of date programs, and 2 that updated were cygrunsrv and cron. After that update, cron no longer performs anything in my crontab once the PC has been hibernated and then turned back on. Rebooting or restrting cron by executing "cygrunsrv -E cron" then "cygrunsrv -S cron" fixes the problem everytime. The ps output always shows cron even when cron doesn't work.
>>>
>>>I've tried reverting to older cron and cygrunsrv in all combinations and none of it fixed the problem. I've looked over the problem reports and saw nothing there either. I've run the most recent cron_check.sh and it reports no problems.
>>>
>>>I've attached the cygcheck output, but not my crontab since it works correctly after the cron restarts so I doubt it's the problem.
>>
>>Do you google?
>><http://www.cygwin.com/ml/cygwin/2003-10/msg00978.html>
>
>Could be my problem, but as I mentioned it had worked flawlessly for at least a year even with daily hibernation until just very recently, so I'd be surprised if that is the cause of my problem. But on the other hand, being an experienced software engineer I know stranger things do happen, so you never know.


Well, that seems to be the latest wisdom on this issue, unless someone 
else pipes up with some more specific debugging that would suggest otherwise.
Of course, that doesn't mean there isn't a solution.  But this post would
suggest that the problem isn't Cygwin-specific.


>>For future reference, this list prefers that you *attach* the output of cygcheck rather than including it in the context of the email message. Attaching helps limit 'false positive' hits when searching the archives.
>>TIA for you help in this matter.
>
>I did attach it as I have been a long time reader of this list and knew of this recommendation. It does show as an attachment in the digest I received this morning. TIA yourself Larry.


You're welcome.  It doesn't show up as an attachment for me (that's fine)
or the email archives (which I checked before commenting).  Guess that's
an issue for the archives, as Igor pointed out.



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/