X-Spam-Check-By: sourceware.org
Date: Wed, 29 Mar 2006 13:16:48 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: informal report on "fork: Resource temporarily unavailable" incidents
Message-ID: <20060329111648.GV20907@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <200603290029.k2T0Tvt3019354@tigris.pounder.sol.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200603290029.k2T0Tvt3019354@tigris.pounder.sol.net>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
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

On Mar 28 18:29, Tom Rodman wrote:
> Not expecting help, just sharing.
> 
> We're running windows 2003 server enterprise edition on a quad processor
> HP proliant G3. uname -a results in 
> [CYGWIN_NT-5.2 c7mdcs063 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin].
> 
> Yesterday I ran a script (kicked off in a makefile) to create /etc/passwd
> for a subset of users in our domain.  It failed w/fork errors (see below).
> After the errors showed up I simplified the script by building
> and running a script like:
> 
>   #!/bin/bash
>   mkpasswd -d -u username1
>   mkpasswd -d -u username2
>   mkpasswd -d -u username3
>   .
>   .
> 
> This script (search ahead for "r7867") had about 400 uniq usernames.
> When I ran it on Monday it also failed w/fork errors on random lines.
> 
> When the problem was happening there were ~105 processes running.
> "net start|wc -l" shows 66 services.
> 
> what apparently fixed the problem:
> 
>   This Tuesday morning I came in, I resumed and then closed the vim
>   sessions, closed the ssh sessions, then opened a new ssh session,
>   and then ran the more complex script 100 times in a row and it never
>   failed. Tonight I opened the same files in vim sessions, suspended
>   them, and then ran the job once and it worked fine.
> 
> We're rebooting the server tonight - it's been up just over 1 week.
> 
> Should I try a later snapshot?

That's always a good idea.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

