X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Date: Thu, 8 Mar 2012 16:11:51 +0100
From: Ulf-Dietrich Braumann <braumann@uni-leipzig.de>
Reply-To: braumann@uni-leipzig.de
To: cygwin@cygwin.com
Subject: Re: 1.7.10 cygrunsrv.exe fails with "fork: 11, Resource temporarily unavailable"
In-Reply-To: <20120308103625.GV5159@calimero.vinschen.de>
Message-ID: <alpine.WNT.2.01.1203081552060.2864@zbpxnh.vmov.hav-yrvcmvt.qr>
References: <4F51BDA2.1040108@cygwin.com> <Pine.WNT.4.64.1203032002030.5532@zbpxnh.vmov.hav-yrvcmvt.qr> <20120304114922.GA18852@calimero.vinschen.de> <Pine.CYG.4.58.1203041425290.2588@zbpxnh.vmov.hav-yrvcmvt.qr> <20120305163158.GT18852@calimero.vinschen.de> <4F54F8D6.3040203@cwilson.fastmail.fm> <20120305173953.GW18852@calimero.vinschen.de> <20120307114321.GA14210@calimero.vinschen.de> <alpine.WNT.2.01.1203081100050.7136@zbpxnh.vmov.hav-yrvcmvt.qr> <alpine.WNT.2.01.1203081114010.6884@zbpxnh.vmov.hav-yrvcmvt.qr> <20120308103625.GV5159@calimero.vinschen.de>
User-Agent: Alpine 2.01 (WNT 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Thanks, Corinna, for asking if sshd was called with the -D option. This 
was the point, although I do not really know why -D was missing (I used 
ssh-host-config).

This is was came out before (sshd in fact was running):

$ cygrunsrv -Q sshd
Service             : sshd
Display name        : CYGWIN sshd
Current State       : Stopped
Command             : /usr/sbin/sshd

Then I removed the service:

$ sc delete sshd
[SC] DeleteService SUCCESS

Then I rerun the installation script (only selected the service 
re-install, of course using the cyg_server account for Win2k3):

$ ssh-host-config
...
*** Info: Host configuration finished. Have fun!
$ cygrunsrv -S sshd
$ cygrunsrv -Q sshd
Service             : sshd
Display name        : CYGWIN sshd
Current State       : Running
Controls Accepted   : Stop
Command             : /usr/sbin/sshd -D

I guess, when I was installing the service before, I may have changed 
something in the Properties menu of the CYGWIN sshd service, perhaps I 
tested something under the SYSTEM account and then have reverted to the 
cyg_server account, so by this action finally the -D may got lost for the 
call of sshd. BTW, I do not actually understand the meaning of -D (When 
this option is specified, sshd will not detach and does not become a 
daemon. This allows easy monitoring of sshd.)

Thank you again - Ulf-Dietrich


On Thu, 8 Mar 2012, Corinna Vinschen wrote:

> That doesn't happen for me.  Does your service entry for sshd omit the 
> -D option?  What does `cygrunsrv -Q sshd' print?  That should look like:
>
>  $ cygrunsrv -Q sshd
>  Service             : sshd
>  Display name        : CYGWIN sshd
>  Current State       : [...]
>  Command             : /usr/sbin/sshd -D
>
> Corinna


> On Mar  8 11:21, Ulf-Dietrich Braumann wrote:
> 
>> Well, while sshd now can be launched again by cygrunsrv, still the 
>> mechanism behaves weird, in the event viewer sshd tells me to be 
>> stopped short after it was started,

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

