all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: dmd: running as non-root user
Date: Fri, 24 Jan 2014 22:29:56 +0100	[thread overview]
Message-ID: <87vbx9xe3v.fsf@gnu.org> (raw)
In-Reply-To: <874n4t2szv.fsf@gmail.com> (Alex Sassmannshausen's message of "Fri, 24 Jan 2014 18:24:04 +0100")

Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:

> Running dmd as a non-privileged user currently results in (by default):
> - log: ~/.dmd.log
> - config: ~/.dmdconf.scm
> - an attempt being made to create a socket at
>   $LOCALSTATEDIRE/var/run/dmd/socket, which fails because poor muggins
>   has no write permissions there (from what I can tell).
>
> I would propose changing the above, Emacs stylee, so that we get the
> following by default:
> - log: ~/.dmd/dmd.log
> - config: ~/.dmd/init.scm (or dmdconf.scm if preferred, though init is
>   probably better known to people familiar with emacs.)
> - socket: ~/.dmd/socket

That makes sense, yes.

(I realized I’m running dmd unprivileged with --prefix=$HOME/foo, so it
had no problem with the socket directory.  But that’s definitely not the
common case.)

[...]

> I think that would make it a more useful tool for managing your own
> daemons, and it would also become more newbie friendly.

Agreed.

> I'm happy to implement the above, or whatever comes out of this
> discussion.
>
> What do you think?

I think it’s a good idea!  :-)  The relevant bits are in support.scm.

Thanks,
Ludo’.

      reply	other threads:[~2014-01-24 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 17:24 dmd: running as non-root user Alex Sassmannshausen
2014-01-24 21:29 ` Ludovic Courtès [this message]

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=87vbx9xe3v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alex.sassmannshausen@gmail.com \
    --cc=guix-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 external index

	https://git.savannah.gnu.org/cgit/guix.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.