From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Defining user services in Guix.
Date: Sun, 23 Apr 2017 01:06:23 +0200 [thread overview]
Message-ID: <878tmsghzk.fsf@gnu.org> (raw)
In-Reply-To: <20170422203131.610f2a30@scratchpost.org> (Danny Milosavljevic's message of "Sat, 22 Apr 2017 20:31:31 +0200")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> personally, I'd just start it inside ~/.xinitrc, ~/.xsession, ~/.fluxbox/startup or similar. That's a little old-school, though, but it's how I always did those things. The disadvantage is that if redshift crashes, it's not being brought back up.
>
> But you can start your own shepherd under your user account and have that shepherd manage user services - it's nice.
That’s exactly what I do.
Surely we could do better, like providing unprivileged users with a tool
akin to ‘guix system reconfigure’ but to manage their own services.
This came up several times in the past.
Ideas?
Ludo’.
next prev parent reply other threads:[~2017-04-22 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 16:50 Defining user services in Guix Mathieu Othacehe
2017-04-22 18:31 ` Danny Milosavljevic
2017-04-22 23:06 ` Ludovic Courtès [this message]
2017-04-23 16:27 ` Mathieu Othacehe
2017-04-25 0:02 ` Mekeor Melire
2017-04-25 8:36 ` Ricardo Wurmus
2017-04-27 13:36 ` Ludovic Courtès
2017-04-28 15:22 ` Mathieu Othacehe
2017-05-02 10:02 ` Ludovic Courtès
2017-05-02 19:23 ` Mathieu Othacehe
2017-05-02 21:21 ` Ludovic Courtès
2017-05-02 21:44 ` Ricardo Wurmus
2017-05-03 9:43 ` Mathieu Othacehe
2017-06-11 1:29 ` Invoking user shepherd; Was: Re: Defining *user* " Danny Milosavljevic
2017-06-11 8:33 ` Mathieu Othacehe
2017-06-13 8:00 ` Ludovic Courtès
2017-06-13 8:06 ` Ludovic Courtès
2017-06-13 14:32 ` Danny Milosavljevic
2017-06-13 16:06 ` Ludovic Courtès
2017-05-02 21:22 ` Defining user " Ludovic Courtès
2017-04-22 23:53 ` Carlo Zancanaro
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tmsghzk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).