From: Paul Eggert <eggert@cs.ucla.edu>
To: 23808@debbugs.gnu.org
Subject: bug#23808: Emacs 25 open-network-stream, make-network-process
Date: Mon, 20 Jun 2016 12:08:35 +0200 [thread overview]
Message-ID: <5767C0A3.9010902@cs.ucla.edu> (raw)
[I'm passing this along from a correspondent who wishes to remain
anonymous.]
Hello, the recent changes to make-network-process (between jan and the
end of april) may have introduced some problems, (I think they may
still be current, apologies otherwise)
I. misreporting the status of a failed network connection: when
open-network-stream is interrupted after `SYN_SENT': For example:
1. $ iptables -A OUTPUT -p tcp --dport 6697 -j DROP -d 127.0.0.1
2. $ nc -v localhost 6697 #;hangs
3. (open-network-stream "test-proc" "test-buffer" "127.0.0.1" 6697) ; ^G
4. (list-processes)
5. (process-status "test-proc") ; open
6. (process-send-string "test-proc" "foo") ; error fd closed
7. (delete-process "test-proc")
For testing on linux, step 1 makes connections to localhost:6697 hang,
step 2 verifies this using `netcat'. interrupt step 3 with a ^G, step
4 lists a spurious "test-proc" which should not exist, and step 5
reports its state as 'open, while step 6 confirms the fd is closed.
II. spurious "server-client-test" processes with
1. emacs --daemon -Q
2. emacsclient -t
3. list-processes
AFAICT from server.el these processes should not exist. Sometimes I've
seen half a dozen of these "server-client-test" processes when the
daemon was slow to start up with multiple clients connecting.
next reply other threads:[~2016-06-20 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 10:08 Paul Eggert [this message]
2016-06-20 12:41 ` bug#23808: Emacs 25 open-network-stream, make-network-process Lars Ingebrigtsen
2016-06-20 22:03 ` Paul Eggert
2016-08-11 9:14 ` Paul Eggert
2016-08-11 10:41 ` Lars Ingebrigtsen
2016-08-11 10:42 ` Lars Ingebrigtsen
2016-08-11 18:26 ` Paul Eggert
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=5767C0A3.9010902@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=23808@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.