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: Wed, 20 Apr 2005 18:53:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: bash/fork problem on Win server 2003 with terminal serve Message-ID: <20050420165320.GE16098@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050415134734 DOT GB15933 AT cygbert DOT vinschen DOT de> <20050420135638 DOT GA16098 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Apr 20 17:19, Lionel B wrote: > "Corinna Vinschen" wrote in message news:20050420135638 DOT GA16098 AT cygbert DOT vinschen DOT de... > > On Apr 20 14:09, Lionel B wrote: > > > "Lionel B" wrote... > > > > "Corinna Vinschen" wrote... > > > > > On Apr 14 14:55, Lionel B wrote: > > > > > > Hi, > > > > > > > > > > > > I seem to have hit the same issue as described in: > > > > > > > > > > > > http://sourceware.org/ml/cygwin/2005-03/msg00919.html > > > > > > > > > > Please test the latest snapshot from http://cygwin.com/snapshots/ > > > > > > > > Thanks, it appears to fix the problem. Will test more thoroughly. > > > > > > Just checking: the fix doesn't appear to have made it into the 1.5.15-1 release - is that correct? > > > > No. > > Ok: the problem as reported in my original post in this thread appears still to exist in 1.5.15. Example: > > bash-2.05b$ ls > 185071245 [main] bash 2892 fork_parent: child 3584 died waiting for longjmp before initialization > bash: fork: No such file or directory > > Cygcheck output attached (again, from a W2K machine on which latest Cygwin is installed rather than the Server 2003 > machine, since the problem prevents me from running cygcheck there). Not helpful. First it's the wrong machine, second it's the wrong Cygwin version, third cygcheck will run since it's not a Cygwin application. If not, something else is wrong on that machine. Oh, forth, it also would run in a local session or if you remotely log in as admin. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/