X-Spam-Check-By: sourceware.org
Message-ID: <45B67293.C9A30FBC@dessent.net>
Date: Tue, 23 Jan 2007 12:39:47 -0800
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Can't start cron daemon in Cygwin 1.5.23 under WinXP SP2
References: <uwt3eznym DOT fsf AT sanofi-aventis DOT com> 	<45B545C3 DOT DF70C019 AT dessent DOT net> 	<17845 DOT 36409 DOT 265000 DOT 733500 AT sanofi-aventis DOT com> 	<009501c73f02$d6383200$3e0010ac AT wirelessworld DOT airvananet DOT com> <uirexzerl DOT fsf AT sanofi-aventis DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Steve Rowley wrote:

> cron: PID 4388: starting service `cron' failed: fork: 11, Resource temporarily unavailable.
> 
> It's starting to look to me as though the problem is either at the
> cygrunsrv level or the WinXP level.

The problem is that the fork call is failing when cygrunsrv tries to
launch cron.  There are a number of reasons that fork might fail, but
normally when this occurs you see it happen in your normal user account,
not just when SYSTEM tries to do it, which I take it is not happening
here.

Dave already mentioned a number of known software programs that cause
fork failures, and I take it they have been ruled out.

The next thing I'd try would be running rebaseall, which involves
installing the rebase package, stopping all Cygwin binaries, then
running the rebaseall script from an ash shell.  (There are directions
in the README.)

If *that* fails, then I'd try getting a SYSTEM-owned bash shell and
seeing if you see general fork failures there.  The method to do this is
a little silly, but I think there is a simple script available to
automate it if you search the archives for "sysbash".

You might also try the latest snapshot of the cygwin DLL, but I'm not
sure there's anything relevant that has changed.  It's still worth doing
though if you can't get it working.

Brian

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