From: Taylor Blau <me@ttaylorr.com>
To: Max Amelchenko <maxamel2002@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
git@vger.kernel.org,
Hideaki Yoshifuji <hideaki.yoshifuji@miraclelinux.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [bug] git clone command leaves orphaned ssh process
Date: Sun, 10 Sep 2023 14:47:23 -0400 [thread overview]
Message-ID: <ZP4PO+HkbsbuKact@nand.local> (raw)
In-Reply-To: <CAN47KsUe=qicr4wZWd33EV+cciUr8ztP2veoOkcw0JBtvsBGjw@mail.gmail.com>
On Sun, Sep 10, 2023 at 12:47:14PM +0300, Max Amelchenko wrote:
> Output of second ps aux command (after running git clone):
>
> bash-4.2# ps aux
>
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
>
> root 1 0.0 0.0 715708 5144 pts/0 Ssl+ 09:43 0:00
> /usr/local/bin/aws-lambda-rie /var/runtime/bootstrap
>
> root 14 0.0 0.0 114096 3088 pts/1 Ss 09:43 0:00 bash
>
> root 167 0.5 0.0 0 0 pts/1 Z 09:46 0:00 [ssh] <defunct>
>
> root 168 0.0 0.0 118296 3408 pts/1 R+ 09:46 0:00 ps aux
>
> See the added ssh defunct process.
Hmm... I wasn't quite able to reproduce this locally. Below
`git.compile` points to a Git executable built from the v2.40.1 tag
corresponding to your bug report:
$ host='ssh://*****@*****lab-prod.server.sim.cloud/terraform/modules/aws-eks'
$ git.compile clone "$host" /tmp/x
Cloning into '/tmp/x'...
ssh: Could not resolve hostname *****lab-prod.server.sim.cloud: Name or service not known
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
and then:
$ ps aux | grep defunct
ttaylorr 3688844 0.0 0.0 6340 2180 pts/1 S+ 14:45 0:00 grep --color defunct
Thanks,
Taylor
next prev parent reply other threads:[~2023-09-10 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 6:38 [bug] git clone command leaves orphaned ssh process Max Amelchenko
2023-09-10 8:50 ` Bagas Sanjaya
2023-09-10 9:47 ` Max Amelchenko
2023-09-10 18:47 ` Taylor Blau [this message]
2023-09-11 10:11 ` Max Amelchenko
2023-09-12 0:40 ` Aaron Schrab
2023-09-12 4:33 ` Jeff King
2023-09-24 10:25 ` Max Amelchenko
2023-09-25 12:29 ` Jeff King
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=ZP4PO+HkbsbuKact@nand.local \
--to=me@ttaylorr.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=maxamel2002@gmail.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 NNTP newsgroup(s).