From: phillip.lord@russet.org.uk
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: bug-gnu-emacs
<bug-gnu-emacs-bounces+phillip.lord=russet.org.uk@gnu.org>,
mah@everybody.org, 36598@debbugs.gnu.org
Subject: bug#36598: 26.1; (error "‘/tmp/emacs1000’ is not a safe directory because it is a symlink")
Date: Sat, 13 Jul 2019 15:30:50 +0100 [thread overview]
Message-ID: <ec249f1578a2d00c8f7c161bc037f7d6@russet.org.uk> (raw)
In-Reply-To: <87k1cmwnu6.fsf@mouse.gnus.org>
On 2019-07-13 05:38, Lars Ingebrigtsen wrote:
> mah@everybody.org (Mark A. Hershberger) writes:
>
>> $ ls -l /tmp/emacs1000
>> lrwxrwxrwx 1 mah mah 20 Jul 11 09:53 /tmp/emacs1000 ->
>> /run/user/1000/emacs
>>
>> Whoever set up the symlink for /tmp/emacs1000 should also change the
>> value of server-socket-dir.
>
> I'm unable to reproduce this error -- do you have a recipe starting
> from
> "emacs -Q"?
>
> What is it that triggers the "is not a safe directory because it is a
> symlink" error? Do you have a backtrace?
I discovered the cause of this the other day.
Launch emacs-27, start the server. Now launch emacs-26 and start the
server with a different. The problem is that
emacs-27 creates the file /tmp/emacs($PID) as a symlink, while emacs-26
doesn't like it.
Probably created by
b663c837249 (Stefan Monnier 2019-05-03 538)
Phil
next prev parent reply other threads:[~2019-07-13 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 14:10 bug#36598: 26.1; (error "‘/tmp/emacs1000’ is not a safe directory because it is a symlink") Mark A. Hershberger
2019-07-13 4:38 ` Lars Ingebrigtsen
2019-07-13 14:30 ` phillip.lord [this message]
2019-07-13 14:45 ` Lars Ingebrigtsen
2019-07-13 15:56 ` phillip.lord
2019-07-14 1:43 ` Glenn Morris
2019-07-14 11:44 ` Lars Ingebrigtsen
2019-07-14 19:11 ` phillip.lord
2019-07-15 13:04 ` Stefan Monnier
2019-07-18 6:27 ` Eli Zaretskii
2019-07-23 12:07 ` Noam Postavsky
2019-07-13 12:46 ` Noam Postavsky
2019-07-13 13:06 ` Lars Ingebrigtsen
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=ec249f1578a2d00c8f7c161bc037f7d6@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=36598@debbugs.gnu.org \
--cc=bug-gnu-emacs-bounces+phillip.lord=russet.org.uk@gnu.org \
--cc=larsi@gnus.org \
--cc=mah@everybody.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 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).