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:	<000501c14699$b9d46690$5d754789@edinstonehaven>
From:	"Keith Starsmeare" <keith_starsmeare AT yahoo DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
Subject:	//c - Ouch!
Date:	Wed, 26 Sep 2001 15:44:19 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

I just updated a colleagues cygwin and couldn't immediately figure out why
it was going so very slowly. The reason - //c references in the path. Every
time a command was issued that searched past that reference it would freeze
because it now scans the network. Ouch!

Also, this opens the (remote) possibility of unscrupulous, twisted people
calling their machines 'C' to catch people out!

I guess we knew this was going to happen, but I wish that there was a way to
temporarily issue some kind of big, unmissable warning somewhere! (But I'm
not volunteering, I can't think of where would be the best place - setup,
bash maybe?)

Keith


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -