From: emacsq via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53814@debbugs.gnu.org
Subject: bug#53814: process-status returns invalid/undocumented status file-error for network process
Date: Sun, 06 Feb 2022 10:44:05 +0000 [thread overview]
Message-ID: <X-LUwG3U455dtxhekJsHlH9T0xw80_I9uidPhoI3350lK-M8HSaDc_EnZ-SunHZkd6JLRLeLxsNEjqrKcbhuo5KsznvRWxKK_owCoKBW9Ck=@protonmail.com> (raw)
In-Reply-To: <-ejTwlwSAZHwKfzZZGDR7XPlHefJ7smDjLy3BOHW66oB1-7iUBOsqY09uHYjt9HL6BZ9f3-54MMMbs04SGv_v7xKZYL9qOk24aUKQVl1Qj8=@protonmail.com>
>
> Apparently, process.c does set this this invalid status for some
> reason:
>
> Lisp_Object data = get_file_errno_data (err, contact, xerrno);
> pset_status (p, list2 (Fcar (data), Fcdr (data)));
> unbind_to (count, Qnil);
> return;
>
So process.c sets the status to file-error, and it also has
error message obtained via get_file_errno_data.
I checked what it says for such a process:
("make client process failed" "Too many open files" :name "example.com" ...)
So I guess it's a too many open connections error, but instead of
saying that, it sets the status to the undocumented file-error.
What's strange is when I delete such a 'file-error' process from
the process list, then it immediately goes to connect and then open
state for the given domain, which is not clear for me how it is
possible, since delete-process removes the process from the list
of processes.
next prev parent reply other threads:[~2022-02-06 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 7:26 bug#53814: process-status returns invalid/undocumented status file-error for network process emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-06 10:44 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-06 12:32 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-06 23:26 ` Lars Ingebrigtsen
2022-02-06 23:27 ` Lars Ingebrigtsen
2022-02-07 6:39 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='X-LUwG3U455dtxhekJsHlH9T0xw80_I9uidPhoI3350lK-M8HSaDc_EnZ-SunHZkd6JLRLeLxsNEjqrKcbhuo5KsznvRWxKK_owCoKBW9Ck=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=53814@debbugs.gnu.org \
--cc=laszlomail@protonmail.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 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.