From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Invoking user shepherd; Was: Re: Defining *user* services in Guix
Date: Tue, 13 Jun 2017 10:00:51 +0200 [thread overview]
Message-ID: <87o9ts48r0.fsf@gnu.org> (raw)
In-Reply-To: <877f0iorer.fsf@gmail.com> (Mathieu Othacehe's message of "Sun, 11 Jun 2017 10:33:00 +0200")
Hello!
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
> I wrote a first draft of user services a month ago. The idea here is
> that guix user -r user-manifest.scm generates a script that lauches a
> user shepherd.
>
> For instance with the following user-manifest.scm :
>
> (define (redshift-service config)
> (list (shepherd-service
> (documentation "Run redshift.")
> (provision '(redshift-test))
> (requirement '())
> (start #~(make-forkexec-constructor
> (list (string-append #$redshift "/bin/redshift")
> "-l" "48:2")))
> (stop #~(make-kill-destructor)))))
>
> (define redshift-service-type
> (service-type
> (name 'test-user)
> (extensions
> (list
> (service-extension shepherd-user-service-type
> test-shepherd-service)))))
>
> (user-configuration
> (services (list (service redshift-service-type #f))))
>
> I get a script that lauches shepherd himself starting redshift.
So you do “guix user user-manifest.scm” and it generates shepherd.conf
and spawns shepherd, right? Sounds pretty cool!
> The plan here was to add a symlink, (don't know where !), pointing to
> the last generated shepherd script, and have the user start shepherd by
> executing the script pointed by the symlink in his .xinitrc for
> instance.
Maybe ~/.config/guix/services/start could be that symlink (and an
indirect GC root.)
Nice work!
Ludo’.
next prev parent reply other threads:[~2017-06-13 8:01 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
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 [this message]
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=87o9ts48r0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=m.othacehe@gmail.com \
/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).