X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <dd3cefac0806151716q6f9b946ey26bf25023647457f@mail.gmail.com>
Date: Mon, 16 Jun 2008 01:16:11 +0100
From: "Adam Thompson" <adwulf AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Fork: Resource temporarily unavailable
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-IsSubscribed: yes
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

Dear all,

We have several sshd installations based on Cygwin, running on Server
2003 SP1 (and also SP2).

Over the last 12 months or so, there seems to have been a lot of
problems with sshd - the eventlogs cite a fork: resource temporarily
unavailable - error.

I've checked the obvious (ie port 22/tcp isn't already bound
elsewhere, ran filemon/regmon) but failed to find the reason.  Is
there a way of logging _which_ resource is temporarily (or rather,
persistently) unavailable?

There seems to be a higher occurrence of this issue on Citrix PS
4.0/4.5 presentation servers, but after ruling out various memory and
cpu optimisations (eg DLL rebasing - I've tried the rebaseall script
and confirmed that none of the sshd or cygrunsrv dependencies have
been touched by Citrix MPS), I can't pin it down to a specific patch
level or configuration.

I've seen various other threads relating to this issue, but no
solution.  I'd like to find the solution, but I seem to be missing
some vital pieces of the puzzle.

I have a nasty feeling this is going to involve learning a bit more
about understanding the drwtsn32.exe crashdumps (manually attaching
the debugger, as crashdumps aren't a symptom of this issue).

Thanks in advance - for any pointers/hints,

-- 
AdamT
"At times one remains faithful to a cause only because its opponents
do not cease to be insipid." - Nietzsche

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