From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59075 invoked by alias); 27 Sep 2019 23:18:58 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 58929 invoked by uid 89); 27 Sep 2019 23:18:49 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=H*M:7550, agent X-HELO: endymion.arp.harvard.edu Received: from endymion.arp.harvard.edu (HELO endymion.arp.harvard.edu) (140.247.179.94) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 27 Sep 2019 23:18:48 +0000 Received: from [192.168.7.23] (pool-74-104-152-231.bstnma.fios.verizon.net [74.104.152.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by endymion.arp.harvard.edu (Postfix) with ESMTPSA id 4C0B66C00C2 for ; Fri, 27 Sep 2019 19:18:46 -0400 (EDT) Subject: Re: ssh-agent doesn't die To: cygwin@cygwin.com References: <319e26c0-32f0-40b7-2137-c7de170a3486@rl.ac.uk> <5b225738-c2d7-fbfe-48a7-8c2a38c3398c@cornell.edu> <0ccd17b6-c22a-1a18-9409-1ebcfae60868@huarp.harvard.edu> <9f7a14bb-f81b-c566-bb84-8da7fc6d0fad@cornell.edu> From: Norton Allen Message-ID: <062f458f-6733-7550-7e87-f12f60e6cc12@huarp.harvard.edu> Date: Fri, 27 Sep 2019 23:59:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-09/txt/msg00276.txt.bz2 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