unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: expressions
Date: 07 Jan 2003 11:11:42 +0100	[thread overview]
Message-ID: <5xwulhxo9t.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <m38yxyc93h.fsf@woof.play-bow.org>

Bob Halley <halley@play-bow.org> writes:

> chad <y@mit.edu> writes:
> 
> > I would expect that the reason /tmp was chosen was the inability of some
> > systems to create sockets in NFS/AFS/SFS/Coda/whatever remote filesystem
> > that the suer might be using for $HOME.  

On a disk-less work station, even /tmp may be on a remote filesystem...

>                                            I suspect that this might still
> > be a problem.  The ssh/openssh technique involves creating a directory
> > in $TMPDIR named ssh-$unique (with other refinements that I think do not
> > apply).  Perhaps this would be a safer strategy?
> 
> Good point, though we don't want a unique name like SSH since we're
> trying to rendezvous on the name.  I tested creating sockets on an NFS
> mounted directory with Solaris and it worked, but I have no idea what
> happens with other platforms or filesystem types.
> 
> So, if we're using /tmp, and want to keep the UID in there for reasons
> RMS explained in another message, 

I didn't see that message...  Was it copied to the list?


>                                   maybe we want something like
> 
>         /tmp/.eserv-<UID>-<HOSTNAME>/server
> 
> which should cover us against pretty much everything :).

In that case, I would suggest naming it something like:

        /tmp/.emacs-UID/server-HOSTNAME

This would give us a standard place in /tmp/.emacs-UID for other
per-user stuff that we may need in the future.  The directory name
should be put in a new lisp variable, e.g. user-private-directory,
which is bound on start-up.

(defcustom user-private-directory (expand-file-name (format "/tmp/.emacs-%d" (user-uid)))
  "*Directory for user private files."
  :set (lambda (...)
        ... create & set modes on the directory if it doesn't exist ...)
  ...)


server.el could then use that variable to create the name of the socket.

(defvar server-socket-name
  (format "%s/server-%s" user-private-directory
	  (substring (system-name) 0 (string-match "\\." (system-name)))))

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2003-01-07 10:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E18UCGO-0002vU-00@snap.thunk.org>
2003-01-05 18:34 ` expressions Richard Stallman
2003-01-05 19:55   ` expressions Bob Halley
2003-01-06  0:49     ` expressions Kim F. Storm
2003-01-06  1:55       ` expressions Bob Halley
2003-01-06 20:06         ` expressions chad
2003-01-06 20:32           ` expressions Bob Halley
2003-01-07 10:11             ` Kim F. Storm [this message]
2003-01-07 19:23               ` expressions Luc Teirlinck
2003-01-11 19:48               ` expressions Stefan Monnier
2003-01-07 10:14       ` expressions Kai Großjohann
2003-01-06 17:13     ` expressions Richard Stallman
2003-01-06 20:37       ` expressions Bob Halley
2003-01-08 21:00       ` expressions Andreas Schwab
2003-01-07 11:53     ` expressions Theodore Ts'o
2003-01-08  8:00       ` expressions Richard Stallman
2003-01-11 19:47       ` expressions Stefan Monnier
2003-01-08 13:50 ` Suggested enhancement: allow emacsclient to send arbitrary LISP expressions Kim F. Storm
2003-01-09 23:13   ` Richard Stallman
2003-01-13 21:08     ` Theodore Ts'o
2003-01-14 18:55       ` Richard Stallman

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=5xwulhxo9t.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@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 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).