Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20001013151952.02305280@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Fri, 13 Oct 2000 15:24:12 -0400
To:	"Farmer, Tony" <FarmerT AT ally DOT com>, "'Earnie Boyd'" <earnie_boyd AT yahoo DOT com>,
	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	RE: WinNT Lockup
In-Reply-To:	<555095BDC488D21192E600104B66477302D43E48@smtp.ally.com>
Mime-Version:	1.0

Bash would eventually have something similar to say.  Once all the 
directories listed in PATH are checked or time out, bash will give something
like "file not found".  Assuming the PATH variable for bash is the same as
in CMD (which it doesn't have to be and is not by default, if I remember
correctly), bash will still be a bit slower than CMD searching for the same
command since it has to go through emulation code in Cygwin.  Some of the
path handling code is not optimal either.

Larry


At 02:52 PM 10/13/2000, Farmer, Tony wrote:
>Thanks, that was definitely the problem.  When you update the FAQ, it would
>be great if you could explain why this symptom only occurs within BASH.  If
>I'm in a regular WinNT command window (with the same active path) and type a
>command that doesn't exist, it says:  "The name specified is not recognized
>as an internal or external command, operable program or batch file."  I
>don't understand why the behavior would be different between the two shells.
>
>Cheers,
>ALF
>
>
> > -----Original Message-----
> > From: Earnie Boyd [SMTP:earnie_boyd AT yahoo DOT com]
> > Sent: Friday, October 13, 2000 11:28 AM
> > To:   Larry Hall (RFK Partners, Inc); Farmer, Tony;
> > 'cygwin AT sourceware DOT cygnus DOT com'
> > Subject:      Re: WinNT Lockup
> > 
> > --- "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com> wrote:
> > > At 01:52 PM 10/13/2000, Farmer, Tony wrote:
> > > >I've setup Cygwin on two systems - one NT and one 98.  The 98 system
> > seems
> > > >to work fine, but on the NT system whenever I type a command that
> > doesn't
> > > >exist ("XXX" for example), Cygwin locks up.  Ctl-C, Ctl-Break, nothing
> > will
> > > >get me out of it short of closing the Cygwin window.  Is this something
> > I'm
> > > >doing wrong or a peculiarity with NT?
> > > >
> > > >Thanks,
> > > >alfarmer AT hotmail DOT com
> > > 
> > > 
> > > Are you sure your path on the NT system doesn't have a network share in
> > it?
> > > The longer the path, the longer the search.  Add several factors for any
> > > network shares in the path.  Add many more factors for network shares
> > that
> > > aren't reachable.  This could look like a "lock up".
> > > 
> > 
> > Good catch Larry.  Sounds like an explaination for the FAQ.
> > 
> > Cheers,
> > Earnie Boyd
> > mailto:earnie_boyd AT yahoo DOT com
> > 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -