From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: ssh-agent doesn't die
Date: Fri, 27 Sep 2019 05:38:00 -0000 [thread overview]
Message-ID: <5b225738-c2d7-fbfe-48a7-8c2a38c3398c@cornell.edu> (raw)
In-Reply-To: <319e26c0-32f0-40b7-2137-c7de170a3486@rl.ac.uk>
On 9/26/2019 7:42 PM, 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.
This does seem like a bug...
> 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
...but this isn't a bug. ssh-agent forks, and then the parent execs the command.
Ken
--
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 2:50 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 [this message]
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
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=5b225738-c2d7-fbfe-48a7-8c2a38c3398c@cornell.edu \
--to=kbrown@cornell.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).