From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Mario Kuechler <mkue@gmx.net>
Cc: cygwin@cygwin.com
Subject: Re: scp slow against cygwin sshd
Date: Thu, 04 Sep 2003 15:33:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0309041128470.1861@slinky.cs.nyu.edu> (raw)
In-Reply-To: <bj7hoo$nhm$1@sea.gmane.org>
On Thu, 4 Sep 2003, Mario Kuechler wrote:
> Christopher Faylor wrote:
> >> Where to start debugging?
> >
> > http://cygwin.com/problems.html
>
> So the first step is the cygcheck output? It's attached.
>
> Regards,
> Mario
Cygwin DLL version info:
DLL version: 1.3.22
^^^^^^
cygwin 1.3.22-1
^^^^^^^^
openssh 3.6.1p1-2
^^^^^^^^^
Does upgrading to the latest Cygwin (1.5.3-1) and openssh (3.6.1p2-2)
solve this problem? It's usually a good idea to upgrade to the latest
version before problem reports.
If the latest Cygwin and openssh don't solve this problem, try running
"scp -vvv" and see if that provides any clues. There's also strace ("man
strace"), which can tell you where the time is going. Please make an
effort to understand and analyze the strace output before dumping gobs of
data to this list.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-09-04 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 11:59 scp slow against Cygwin sshd Mario Kuechler
2003-09-04 13:57 ` scp slow against cygwin sshd Christopher Faylor
2003-09-04 14:21 ` Mario Kuechler
2003-09-04 15:33 ` Igor Pechtchanski [this message]
2003-09-04 16:14 ` Mario Kuechler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0309041128470.1861@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=cygwin@cygwin.com \
--cc=mkue@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).