Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 18 Dec 2003 15:44:45 -0800 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: Forks/spawn test using ~latest~ CVS source 20031217 10:00AM (GMT+1) Message-ID: <20031218234444.GA812@efn.org> References: <20031218230954 DOT GA25465 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031218230954.GA25465@redhat.com> User-Agent: Mutt/1.4i Organization: bs"d X-IsSubscribed: yes On Thu, Dec 18, 2003 at 06:09:54PM -0500, Christopher Faylor wrote: > On Fri, Dec 19, 2003 at 12:04:02AM +0100, Philippe Torche wrote: > >I've tested the CVS source 20031217 10:00AM (GMT+1) to see if fork/spawn > >works on Multi CPU (4 Xeon) with Windows 2003 Server (see old message > >about it in the mailing list). Unfortunatly It doesn't ! > > > >Below a test script, use it by running run_t.sh. After some time (< 1 > >minute) one or more of the 5 sub-shell stop. This batch works perfectly > >using a single P4 cpu on Windows XP ! > > I don't know how many people out there have Multi CPU Xeons, but I > suspect there aren't many. This works fine in my single CPU system, > as you note. > > >Thanks in advance, Philippe. > > > >PS 1 : 4-5th attempt to send a mail to cygwin AT cygwin DOT com using three > >different mail account, gmane newgroup ! Anti-spam ? :( > > Yes. ZIP file attachments. > > >PS 2 : Vital for me that this works before end of the month ! > > Sorry, but why would your urgency have any bearing on a community, > volunteer project? Maybe he's implying there is funding available for working on this if necessary? -- 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/