From: Norton Allen <allen@huarp.harvard.edu>
To: cygwin@cygwin.com
Subject: Re: ssh-agent doesn't die
Date: Fri, 27 Sep 2019 23:59:00 -0000 [thread overview]
Message-ID: <062f458f-6733-7550-7e87-f12f60e6cc12@huarp.harvard.edu> (raw)
In-Reply-To: <a2581894-fea4-fd71-ffbc-b16dbeb671d9@cornell.edu>
On 9/27/2019 11:09 AM, Ken Brown wrote:
> On 9/27/2019 10:27 AM, Vanda Vodkamilkevich wrote:
>> Hi,
>> this may probably be not fully related but I see from time to time a
>> strange behavior of ssh-agent (running in the background and initially
>> started by keychain launched in .bashrc) : the agent is running wild (25%
>> of cpu and never responding). It seems to occur (not systematically) when
>> network is disconnected and reconnected (this is on a laptop often removed
>> from the docking system). Do you have any idea how to diagnose the issue
>> more precisely?
> Sorry, but I'm not an expert on ssh-agent. Everything I said above is based on
> doing an internet search and looking briefly at the ssh-agent source code.
>
> My only suggestion would be to attach gdb to the process when it starts running
> wild and see if you can figure out why it's inf-looping. If you don't know how
> to do this, someone who does know would have to be able to reproduce the problem.
I am not an ssh-agent expert either, but I can report that I have also
observed this behavior on cygwin. I do not know how to reproduce it.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-09-27 23:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 0:34 Tim Adye
2019-09-27 2:43 ` Norton Allen
2019-09-27 5:38 ` Ken Brown
2019-09-27 14:12 ` Norton Allen
2019-09-27 14:27 ` Ken Brown
2019-09-27 15:09 ` Vanda Vodkamilkevich
2019-09-27 23:18 ` Ken Brown
2019-09-27 23:59 ` Norton Allen [this message]
[not found] ` <185c5774-dd8b-5488-b818-4cec5a24bf2d@cornell.edu>
2019-10-04 14:27 ` Ken Brown
2019-10-04 20:13 ` Ken Brown
2019-11-03 19:01 ` Corinna Vinschen
2019-11-04 11:49 ` Tim Adye
2019-11-04 14:17 ` 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=062f458f-6733-7550-7e87-f12f60e6cc12@huarp.harvard.edu \
--to=allen@huarp.harvard.edu \
--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).