From: Tim Adye <T.J.Adye@rl.ac.uk>
To: <cygwin@cygwin.com>
Subject: Re: ssh-agent doesn't die
Date: Mon, 04 Nov 2019 11:49:00 -0000 [thread overview]
Message-ID: <38e07653-1a09-c398-d2ab-557965046b93@rl.ac.uk> (raw)
In-Reply-To: <20191103190052.GI3372@calimero.vinschen.de>
On 03/11/2019 19:00, Corinna Vinschen wrote:
> On Sep 27 00:42, Tim Adye wrote:
>> 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
>> [...]
>> 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 pushed a patch and created new developer snapshots. Please test the
> latest from https://cygwin.com/snapshots/
Hi Corinna,
That fixes the problem! With cygwin1-20191103.dll.xz installed as
/usr/bin/cygwin1.dll, all my ssh-agent processes exit properly.
> Thanks,
> Corinna
Thanks for the excellent fix,
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
next prev parent reply other threads:[~2019-11-04 11:49 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
[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 [this message]
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=38e07653-1a09-c398-d2ab-557965046b93@rl.ac.uk \
--to=t.j.adye@rl.ac.uk \
--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).