From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 53408 invoked by alias); 26 Sep 2019 23:42:49 -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 53399 invoked by uid 89); 26 Sep 2019 23:42:49 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=Package, fairly, UID, cygwin-patches@cygwin.com X-HELO: smtp-out6.electric.net Received: from smtp-out6.electric.net (HELO smtp-out6.electric.net) (192.162.217.192) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Sep 2019 23:42:47 +0000 Received: from 1iDdPJ-0000CA-TM by out6e.electric.net with emc1-ok (Exim 4.92.2) (envelope-from ) id 1iDdPJ-0000Cb-UT for cygwin@cygwin.com; Thu, 26 Sep 2019 16:42:45 -0700 Received: by emcmailer; Thu, 26 Sep 2019 16:42:45 -0700 Received: from [130.246.132.232] (helo=exchsmtp.stfc.ac.uk) by out6e.electric.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) (Exim 4.92.2) (envelope-from ) id 1iDdPJ-0000CA-TM for cygwin@cygwin.com; Thu, 26 Sep 2019 16:42:45 -0700 Received: from [192.168.0.2] (86.0.81.86) by exch01.fed.cclrc.ac.uk (130.246.132.232) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1531.3; Fri, 27 Sep 2019 00:42:44 +0100 From: Tim Adye Subject: ssh-agent doesn't die To: Message-ID: <319e26c0-32f0-40b7-2137-c7de170a3486@rl.ac.uk> Date: Fri, 27 Sep 2019 00:34:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-EsetResult: clean, is OK X-EsetId: 37303A290F3E23686C7566 X-Outbound-IP: 130.246.132.232 X-Env-From: tim.adye@stfc.ac.uk X-Proto: esmtps X-Revdns: exch01.rl.ac.uk X-TLS: TLSv1.2:ECDHE-RSA-AES256-SHA384:256 X-Authenticated_ID: X-PolicySMART: 3590380 X-IsSubscribed: yes X-SW-Source: 2019-09/txt/msg00264.txt.bz2 Hi, I have noticed a (new?) problem with using ssh-agent to start a session, eg. with   ssh-agent xterm & When the xterm (or whatever) command completes, the ssh-agent process is still left running in the background. It should stop once its subprocess is done. As a simple test example, consider: /bin/ssh-agent /bin/sleep 10 While the sleep is still running, ps shows:       PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND      1694    1693    1694       1576  ?          22534 00:01:10 /usr/bin/ssh-agent      1653       1    1653      11740  cons1      22534 00:00:37 /usr/bin/bash      1693    1653    1693       1552  cons1      22534 00:01:10 /usr/bin/sleep One oddity is that ssh-agent is listed as a subprocess of sleep, not the other way round. pstree shows this clearly: ?-+-bash---pstree   `-bash---sleep---ssh-agent Once the sleep finishes, ps shows:       PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND      1694    1693    1694       1576  ?          22534 00:01:10 /usr/bin/ssh-agent      1653       1    1653      11740  cons1      22534 00:00:37 /usr/bin/bash ie. ssh-agent is still running, though its PPID no longer exists. I'm using the latest release versions of cygwin and openssh: Cygwin Package Information Package              Version        Status cygwin               3.0.7-1        OK openssh              8.0p1-2        OK with Windows 10 1803 (2019-09 update). I use Sophos AV 10.8 with HitmanPro. Previously, I haven't had this problem: ssh-agent stopped when it's subprocess stopped. I updated from Cygwin 2.10-1 (and contemporaneous openssh) fairly recently, and it's possible the problem started then. Or it could have been a Windows minor update, AV update, or some other setting change I made. Sorry I couldn't pin it down further. Is it just me that sees this, or could it be a bug in ssh-agent or Cygwin? If it is just me, my first suspicion would be HitmanPro, which previously caused silent failures with an earlier version of Cygwin (I reported in cygwin-patches@cygwin.com, June 2018). That bug is fixed, but maybe this is something new. If we can rule out a more general Cygwin bug, I can ask my IT support to try disabling the HitmanPro to test. Thanks, Tim. -- 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