Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <m12k0kd-003zI6C@smtp.web.de>
From: "Ulrich Jakobus" <u DOT jakobus AT web DOT de>
To: "cygwin AT sourceware DOT cygnus DOT com" <cygwin AT sourceware DOT cygnus DOT com>
Date: Tue, 25 Apr 2000 10:26:33 +0200
Reply-To: "Ulrich Jakobus" <u DOT jakobus AT web DOT de>
X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows NT (4.0.1381;6)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: CYGWIN-1.1.0 trouble: 40 to 80 sec delay if no network connection

Hello,

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
connection.

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.

Thanks,

Ulrich




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