From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: [PATCH 0/1] MPD: Install systemd service files
Date: Thu, 29 Dec 2016 19:24:19 +0100 [thread overview]
Message-ID: <87lguywq3w.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <cover.1483029229.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Leo Famulari <leo@famulari.name> writes:
> I noticed that MPD 0.19.21 adds a systemd service file for unprivileged
> users:
>
> http://git.musicpd.org/cgit/master/mpd.git/plain/NEWS?h=v0.19.21
>
> It works for me!
>
> This patch installs both the privileged and unprivileged service files.
>
> I wonder, is this installation path correct? Should they be at
>
> ~/.guix-profile/etc/systemd[...] (my patch does this)
Yes. Unit names in managed packages should not conflict, so no further
namespacing necessary. This way users can just sync/link units from
<guix-profile>/etc/systemd/{user,system} to the respective system
locations.
Btw, Shepherd works in user mode too ;-)
Here is a config that defines a service for "mcron":
$ cat ~/.config/shepherd/init.scm
(define mcron (make <service>
#:provides '(mcron)
#:start (make-forkexec-constructor
(list "/run/current-system/profile/bin/mcron"))
#:stop (make-kill-destructor)))
(register-services mcron)
I guess it would be better to re-use the Guix service definition, but
haven't gotten that far yet.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2016-12-29 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 16:34 [PATCH 0/1] MPD: Install systemd service files Leo Famulari
2016-12-29 16:34 ` [PATCH 1/1] gnu: mpd: " Leo Famulari
2016-12-29 18:24 ` Marius Bakke [this message]
2016-12-29 18:35 ` [PATCH 0/1] MPD: " Leo Famulari
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=87lguywq3w.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.