From: Eli Zaretskii <eliz@gnu.org>
To: Henrik Ahlgren <pablo@seestieto.com>,
Michael Albinus <michael.albinus@gmx.de>
Cc: 43226@debbugs.gnu.org
Subject: bug#43226: 28.0.50; Running Tramp tests on MS-Windows leaves zombie processes on the remote
Date: Tue, 25 Oct 2022 22:17:50 +0300 [thread overview]
Message-ID: <83lep3ogpt.fsf@gnu.org> (raw)
In-Reply-To: <871qqwhuqy.fsf@seestieto.com> (message from Henrik Ahlgren on Tue, 25 Oct 2022 16:56:37 +0300)
> From: Henrik Ahlgren <pablo@seestieto.com>
> Cc: 43226@debbugs.gnu.org
> Date: Tue, 25 Oct 2022 16:56:37 +0300
>
> Consider this example that seems to work fine (no cmdproxy involved):
>
> (let ((start-file-process "eoftest" (get-buffer-create "*eoftest*")
> "ssh" "<hostname>" "cat"))
> (sit-for 10)
> (process-send-string sshz "foo")
> (sit-for 5)
> (process-send-eof sshz))
>
> vs this that hangs, leaving cat running forever:
>
> (let ((default-directory "/sshx:<hostname>:/home/my/git/dir")
> (sshz start-file-process "eoftest" (get-buffer-create "*eoftest*")
> "cat"))
> (sit-for 10)
> (process-send-string sshz "foo")
> (sit-for 5)
> (process-send-eof sshz))
>
> The cat process does not even seem to receive any input ("foo") I trace
> it in the remote machine.
Maybe Michael (CC'ed) can explain how this is supposed to work,
because I don't think I understand. The actual process run by Emacs
is ssh, not cat, so how is EOF supposed to get to the remote "cat"?
> ps. I wonder why my emails are not appearing in debbugs?
No clue. Fortunately, Michael also knows about debbugs much more than
I do.
next prev parent reply other threads:[~2022-10-25 19:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 16:38 bug#43226: 28.0.50; Running Tramp tests on MS-Windows leaves zombie processes on the remote Eli Zaretskii
2020-09-05 19:04 ` bug#43226: Fwd: bug#26911: 25.2; eshell "cd .." doesn't work correctly with TRAMP Michael Albinus
2020-09-05 19:04 ` Michael Albinus
2020-09-05 19:16 ` bug#43226: 28.0.50; Running Tramp tests on MS-Windows leaves zombie processes on the remote Michael Albinus
2020-09-05 19:25 ` Eli Zaretskii
2020-09-06 8:49 ` Michael Albinus
2020-09-06 15:14 ` Eli Zaretskii
2020-09-06 15:54 ` Michael Albinus
2020-09-06 16:07 ` Eli Zaretskii
2022-10-25 9:39 ` Henrik Ahlgren
2022-10-25 11:26 ` Eli Zaretskii
2022-10-25 13:56 ` Henrik Ahlgren
2022-10-25 16:49 ` Michael Albinus
2022-10-25 19:17 ` Eli Zaretskii [this message]
2022-10-26 11:34 ` Henrik Ahlgren
2022-10-26 12:01 ` Eli Zaretskii
2022-10-26 14:15 ` HA
2022-10-29 14:48 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lep3ogpt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43226@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=pablo@seestieto.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).