RE: Sergy Okhapkin's scp1 and ssh take 3 minutes to initialize

["Michael Erdely" <cygwin at cygwin dot com>]

Hmm... I'm not sure if it's related to the previous thread we had about
this on http://sources.redhat.com/ml/cygwin/2001-06/msg00428.html where
I state what I THOUGHT was a possible fix.  Since then, the problem has
come back and I'm not sure why.

So, to test this out in more detail, I set up a server using srvany
running as LocalSystem that launches %windir%\system32\cmd.exe.
Basically, a command prompt runs in the foreground as SYSTEM so I can
"see what it can see".

When the window comes up, I change to c:\cygwin\bin.  Checking the
values of my PATH and CYGWIN variables at the CMD prompt, PATH =
C:\Perl\Bin;C:\WINNT;C:\WINNT\System32;C:\WINNT\System32\Webm;C:\Cygwin\
Bin and CYGWIN = ntsec tty.  The C: drive is NTFS.  I've modified the
default permissions of 777 on all files to og-w and removed a-x on
non-executables in the /etc directory.  In addition, SYSTEM:SYSTEM owns
the /etc/ssh_host*_key files with 600 perms.

As far as the PATH, CYGWIN var and directory permissions, I've used this
set up on other machines without issue.

>From the c:\cygwin\bin directory, I just ran ..\cygwin.bat.  It took
"forever" for the prompt to appear.  In fact, I put "date" at the top of
/etc/profile and "forever" occurred before the date was displayed. ;-).
So, I thought, if it _IS_ related to the path, let me make _sure_ it's
correct.  So, added a line in the cygwin.bat file under "@echo off" that
said: set PATH=c:\cygwin\bin;c:\winnt;c:\winnt\system32.  Sill had the
same problems.  I also tried just running bash.exe from the
c:\cygwin\bin directory.  No go.

Under my user context, I can click on the Cygwin Bash Shell icon and the
prompt appears almost instantaneously.

So... I don't believe this to be a OpenSSH related problem at all.  In
my above tests, OpenSSH was never introduced.

Unfortunately, I'm not a coder (or much of a coder, anyway), but I took
a shot at trying to get more information, so I ran "strace bash" both
from the LocalSystem's CMD prompt and from my own CMD prompt (one being
slow in starting bash/cygwin1.dll/... and one being fast).  If they'd be
helpful, I can put them up on my ftp server, they're kind of big.

One other note: I searched all local drives (note: there were no network
directories in my path) for other cygwin1.dll files.  There was one in
the MYSQL directory, but if I'm not mistaken, that one is not used.
>From MySQL manual.txt:
> If you want to use `mysqlc.exe', you must copy
> `C:\mysql\lib\cygwinb19.dll' to your Windows system directory
> (`\windows\system' or similar place).
Well... I'm not using mysqlc.  I was using mysql-nt.exe.  And
"C:\Program Files\MySQL\lib" was not in my path anyway (I did not copy
it to %windir%\system as the manual suggests).  But, to be safe, I
deleted the cygwinb19.dll and stopped the MySQL service anyway.  The
problem still existed.

It may be interesting to note that the only boxen that I've seen this
slow behavior is Win2k Server boxen.  In all cases, the servers are
running Service Pack 1.

Anyone else have any ideas?

-ME

-----Original Message-----
From: cygwin-owner@sources.redhat.com
[mailto:cygwin-owner@sources.redhat.com] On Behalf Of Clark Sims
Sent: Tuesday, June 26, 2001 3:42 PM
To: cygwin@cygwin.com
Subject: Re: Sergy Okhapkin's scp1 and ssh take 3 minutes to initialize

>Why aren't you using the ssh that comes with the cygwin distribution?

I got the ssh, and scp to work that came with the cygwin distribution.
They
have the same problem that Sergy ports have, in that they take a long
time
to connect to the server.


--
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/