Mail Archives: cygwin/2000/04/25/11:00:08
On Tue, 25 Apr 2000 07:15:03 -0700 (PDT), Earnie Boyd wrote:
>--- Ulrich Jakobus <u DOT jakobus AT web DOT de> wrote:
>> 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
>> >starting bash.
>>
>> Unfortunately, this is not the problem. There are only directories on
>> my local hard disk in $PATH. However, the output of "set" also includes
>> variables
>>
>> !0:=0:/home4/jakobus/LAPACK_3.0/BLAS/SRC/
>> !A:='A:\'
>> !D:='D:\cygnus\cygwin-1.1.0\lib\gcc-lib\i686-pc-cygwin\2.95.2'
>> !E:='E:\zip'
>> !\:='\\Ihfbdc\Netzsoftware\FEKO_update'
>>
>> and indeed the "!\:" refers to a network directory. Can this be the
>> reason?
>
>Yes, it could be the reason
>
>> However, this is set only inside bash, not before in my
>> DOS shell, from where I start bash
>
>This is certainly strange. What's contained in the ~/.bashrc file.
I do not have a $HOME/.bashrc or $HOME/.bash_profile at the moment.
It seems to me that with the "!D:" etc. variables mentioned above,
CYGNUS keeps track of the last visited directories on the various
partitions. For instance, now I rebooted and have not accessed
any file on the floppy disk or any file over the network since
rebooting. If I now start a bash session, I only get the following
defined:
!C:='C:\WINNT\Profiles\jakobus.000\Desktop\Programme'
!D:='d:\corel\VERSIONS'
In particular, there is no reference to a network directory, but
still if I remove the network cable and type any CYGNUS command
from a DOS window, I observe a 40 to 80 sec delay.
>
>Ah, we're getting closer to the problem. I expect that Cygwin commands running
>from the DOS prompt to be slightly longer overall. Every instance of the
>command has to load and initialize Cygwin.
Well, I agree, but not that much longer. This should be fractions of
seconds, and it should not make a difference whether my network cable
is attached or not.
>
>You could also try one of the newer snapshots to see if that solves the
>problem.
>
I have tried this now as well (snapshot cygwin-inst-20000421.tar.gz,
version CYGWIN_NT-4.0 1.1.1(0.19/3/2) 2000-04-22 00:15:04 i686 unknown),
same effect.
As a cross test, I went again back to my CYGWIN installation
21.0(0.0/1/1) 1999-1-16 00:09:20, which I still had archived in
a zip file. There I do not observe the delays when the network
cable is not attached.
Cheers,
Ulrich
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -