From: Paul Eggert <eggert@cs.ucla.edu>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 33847@debbugs.gnu.org
Subject: bug#33847: 27.0.50; emacsclient does not find server socket
Date: Sat, 29 Dec 2018 22:47:52 -0800 [thread overview]
Message-ID: <396c1845-b3a1-d0d1-7491-3cef02405f15@cs.ucla.edu> (raw)
In-Reply-To: <w6g8t0a40n3.fsf@kph.uni-mainz.de>
Ulrich Mueller wrote:
> The only problem I see is that it would leave a stale socket file
> behind, when Emacs is not properly terminated. That file would be
> deleted/replaced the next time an Emacs server is started.
>
> I guess in the typical use case we are talking about a single inode.
> If the home directory is NFS mounted it may be one inode per machine.
> I think that's a small price to pay, for a solution that would be both
> very simple, would be available on all systems, and won't suffer from
> security issues.
If we're talking NFS, we will indeed have security issues, not to mention
problems with deleting or replacing files. I can't count the number of times
I've seen messages like "NFS server not responding still trying".
The TCP case is already documented as being undesirable, and this is partly due
to security concerns. We shouldn't inflict its problems on the more-usual local
case.
next prev parent reply other threads:[~2018-12-30 6:47 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 9:48 bug#33847: 27.0.50; emacsclient does not find server socket Ulrich Mueller
2018-12-23 16:20 ` Ulrich Mueller
2018-12-25 21:02 ` Paul Eggert
2018-12-25 23:29 ` Ulrich Mueller
2018-12-26 0:24 ` Paul Eggert
2018-12-26 2:27 ` Ulrich Mueller
2018-12-26 6:59 ` Paul Eggert
2018-12-26 15:14 ` Ulrich Mueller
2018-12-26 18:32 ` Paul Eggert
2018-12-28 6:37 ` Ulrich Mueller
2018-12-30 6:47 ` Paul Eggert [this message]
2018-12-27 3:38 ` Richard Stallman
2018-12-27 16:42 ` Paul Eggert
2018-12-27 17:13 ` Paul Eggert
2018-12-28 6:19 ` Ulrich Mueller
2018-12-28 6:35 ` Paul Eggert
2018-12-28 6:51 ` Ulrich Mueller
2018-12-30 6:44 ` Paul Eggert
2019-01-20 17:59 ` Ulrich Mueller
2019-02-10 8:37 ` Ulrich Mueller
2019-02-10 9:48 ` Eli Zaretskii
2020-08-19 11:05 ` Lars Ingebrigtsen
2020-08-21 21:28 ` Paul Eggert
2020-08-22 7:24 ` Ulrich Mueller
2020-08-22 7:33 ` Andreas Schwab
2020-08-22 7:45 ` Ulrich Mueller
2020-08-22 8:00 ` Eli Zaretskii
2020-08-22 17:51 ` Paul Eggert
2020-08-22 7:59 ` Eli Zaretskii
2020-08-22 17:55 ` Paul Eggert
2020-08-22 18:30 ` Eli Zaretskii
2020-08-22 21:20 ` Paul Eggert
2020-08-23 5:41 ` Eli Zaretskii
2021-07-22 13:08 ` Lars Ingebrigtsen
2021-07-22 16:45 ` Eli Zaretskii
2021-07-22 17:05 ` Lars Ingebrigtsen
2021-07-22 17:30 ` Eli Zaretskii
2021-07-23 11:31 ` Lars Ingebrigtsen
2021-07-23 11:38 ` Lars Ingebrigtsen
2021-07-23 23:58 ` Paul Eggert
2021-07-24 6:23 ` Eli Zaretskii
2021-07-24 7:48 ` Paul Eggert
2021-07-24 8:25 ` Eli Zaretskii
2021-07-24 23:31 ` Paul Eggert
2021-07-25 6:32 ` Eli Zaretskii
2021-07-25 16:22 ` Paul Eggert
[not found] ` <a0688fd6-9e73-73d8-6138-3280981abcb5@cs.ucla.edu>
2021-07-25 16:34 ` Eli Zaretskii
2021-10-04 6:45 ` Paul Eggert
2021-07-25 7:27 ` Eli Zaretskii
2021-07-24 10:11 ` Lars Ingebrigtsen
2021-07-24 19:37 ` Paul Eggert
2021-07-23 11:58 ` Eli Zaretskii
2021-07-22 18:30 ` Ulrich Mueller
2019-04-27 1:41 ` Teika Kazura
2019-04-27 7:56 ` Eli Zaretskii
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=396c1845-b3a1-d0d1-7491-3cef02405f15@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=33847@debbugs.gnu.org \
--cc=ulm@gentoo.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.