This is the mail archive of the
mailing list for the Cygwin project.
Re: CYGWIN-1.1.0 trouble: 40 to 80 sec delay if no network connection
- To: "cygwin at sourceware dot cygnus dot com" <cygwin at sourceware dot cygnus dot com>,"earnie_boyd at yahoo dot com" <earnie_boyd at yahoo dot com>
- Subject: Re: CYGWIN-1.1.0 trouble: 40 to 80 sec delay if no network connection
- From: "Ulrich Jakobus" <u dot jakobus at web dot de>
- Date: Tue, 25 Apr 2000 15:54:00 +0200
- Reply-To: "Ulrich Jakobus" <u dot jakobus at web dot de>
On Tue, 25 Apr 2000 05:18:52 -0700 (PDT), Earnie Boyd wrote:
>Sounds like you've the network paths in your environment PATH. AFAIR, this has
>always been a problem. Try removing the networked paths from PATH before/after
Unfortunately, this is not the problem. There are only directories on
my local hard disk in $PATH. However, the output of "set" also includes
and indeed the "!\:" refers to a network directory. Can this be the
reason? However, this is set only inside bash, not before in my
DOS shell, from where I start bash (I do observe the long delays
only when executing CYGNUS commands from within a DOS window, not
when running them from within BASH).
I also tried to remove other environment variables that might
indicate a network connection, such as LOGONSERVER and USERDOMAIN,
but also no effect with this.
>--- Ulrich Jakobus <firstname.lastname@example.org> wrote:
>> last week I upgraded from CYGWIN B21 to the new net release
>> CYGWIN 1.1.0. I have absolutely no trouble when my computer
>> is connected to the network (Ethernet). However, this is a
>> notebook computer running under Windows NT 4.0 service pack 6,
>> and whenever I work at home I do not have a permanent network
>> The following effect is fully reproducable:
>> If I disconnect my network cable and want to execute any
>> CYGWIN command (e.g. open a bash shell, type "ls" in a DOS
>> window, execute "make" from within emacs etc.), I have to
>> wait for about 40 to 80 seconds, then I get the correct result
>> (e.g. if I type "ls" only after 40 to 80 sec I get the list
>> of files, no error or so is printed). As soon as I attach the
>> network cable again, I get an immediate response. I also
>> can open a bash shell (also delay 40 to 80 sec), but then
>> inside this bash shell I can execute CYGWIN commands and
>> get an immediate response. The same problem applies to
>> applications that I compile with gcc.
>> Does anybody else observe this problem? Any idea how to fix it?
>> I did not have this or similar problems with CYGWIN B21.
>> Want to unsubscribe from this list?
>> Send a message to email@example.com
>Do You Yahoo!?
>Send online invitations with Yahoo! Invites.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org