From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: WG: Re: SSH V.5.1 with Cygwin1.dll 1.7.0(0.189/5/3) 2008-12-09: Very ?large logon times...
Date: Thu, 22 Jan 2009 15:02:00 -0000 [thread overview]
Message-ID: <20090122114202.GD17948@calimero.vinschen.de> (raw)
In-Reply-To: <OFE9BA6636.3ACFB34E-ONC1257545.00575C35-C1257546.002FE213@nbg.sdv.spb.de>
On Jan 22 09:44, Markus.Bauer wrote:
> Hello Corinna,
I already told your collegue Carsten:
Please, don't http://cygwin.com/acronyms/#TOFU
I hope you're aware that cygwin@cygwin.com is a public mailing list?
I'm just asking because you're addressing me personally...
> my name is Markus Bauer. I'm a colleague from Carsten Porzler and I tried
> to figure out where the time is wasted.
> I put some debugging statements in sec_auth.cc and syscalls.cc. The
> strange is, that I only see the statements from syscalls.cc but not the
> many I put in sec_auth.cc.
>
> Maybe you have an idea?
No. Not really. The only reason could be that the code isn't called.
Only further debugging will help.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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:[~2009-01-22 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 11:31 WG: Re: SSH V.5.1 with Cygwin1.dll 1.7.0(0.189/5/3) 2008-12-09: Very large " Markus.Bauer
2009-01-22 15:02 ` Corinna Vinschen [this message]
2009-02-20 14:47 ` SSH V.5.1 with Cygwin1.dll 1.7.0: " Carsten.Porzler
2009-02-20 15:20 ` Corinna Vinschen
2009-02-20 17:10 ` Corinna Vinschen
2009-02-23 15:57 ` SSH V.5.1 with Cygwin1.dll 1.7.0: Very large logon times... ---- SUCCESS!!! Carsten.Porzler
2009-02-23 16:52 ` Corinna Vinschen
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=20090122114202.GD17948@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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).