X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Wilfried <wh_ng AT gmx DOT de>
Subject: Re: 1.7.10 cygrunsrv.exe fails with "fork: 11, Resource temporarily unavailable"
Date: Mon, 05 Mar 2012 11:37:16 +0100
Lines: 43
Message-ID: <da59l7l4htik11mfd5g0p6g96icqmjc8c2@4ax.com>
References: <alpine DOT WNT DOT 2 DOT 01 DOT 1203021514490 DOT 5120 AT zbpxnh DOT vmov DOT hav-yrvcmvt DOT qr> <4F51BDA2 DOT 1040108 AT cygwin DOT com> <Pine DOT WNT DOT 4 DOT 64 DOT 1203032002030 DOT 5532 AT zbpxnh DOT vmov DOT hav-yrvcmvt DOT qr> <20120304114922 DOT GA18852 AT calimero DOT vinschen DOT de> <Pine DOT CYG DOT 4 DOT 58 DOT 1203041425290 DOT 2588 AT zbpxnh DOT vmov DOT hav-yrvcmvt DOT qr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

Ulf-Dietrich Braumann wrote:

> Yes, Corinna, I reverted this setting again to the default 384MB heap size 
> calling:
> 
> $ peflags --cygwin-heap=0 /usr/sbin/sshd.exe
> and
> $ peflags --cygwin-heap=0 /usr/bin/cygrunsrv.exe
> 
> Later on, someone has recommended me to downgrade cygrunsrv from 1.36-1 to 
> 1.34-1. This helped, so now under cygwin1.dll 1.7.11 the sshd can be 
> started. However, the mechanism behaves strange reporting problems:
> 
> C:\>net start sshd
> The CYGWIN sshd service is starting.
> The CYGWIN sshd service could not be started.
> 
> The service did not report an error.
> 
> More help is available by typing NET HELPMSG 3534.
> 
> 
> Having a look into the Event Viewer of my Win2k3 64bit machine, I 
> correspondingly find:
> 
> ... `sshd' service stopped, exit status: 0.
> 
> This however is misleading, since I clearly see the sshd running now (I 
> made sure it was not running before), and indeed I can now connect using 
> slogin and sftp:
> [...]

Hello,
I see the same "misleading message" (`sshd' service stopped) since I am
running sshd on my Windows XP Pro 32bit machine. (currently running
cygrunsrv V1.34, Mar 18 2008
OpenSSH_5.1p1, OpenSSL 0.9.8l 5 Nov 2009)
However I don't bother because several other (Microsoft) services behave
similar, i.e. they are started when Windows is booted and stopped
immediately afterwards. This doesn't prevent them from being started
again when needed.
--
Wilfried Hennings


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple