From: John Soo <jsoo1@asu.edu>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: User-Level services
Date: Sat, 9 Feb 2019 05:14:28 -0800 [thread overview]
Message-ID: <F7063773-FDB5-4422-B443-29393B466A5D@asu.edu> (raw)
In-Reply-To: <87k1i973g9.fsf@gmail.com>
Thanks Chris,
I wasn’t aware of the autostart spec so I took a look. Thanks! After reading it I’m not sure it provides the retry support (among other things) that a user service might provide. I would love to see something closer to an event triggered service than forking once and forgetting.
It would be awesome if the Guix System could provide a way to configure these declaratively, too. I am not saying shepherd would be the mechanism, necessarily either. I just think people - myself included - will probably want this feature.
Thanks again,
John
> On Feb 9, 2019, at 12:48 AM, Chris Marusich <cmmarusich@gmail.com> wrote:
>
> John Soo <jsoo1@asu.edu> writes:
>
>> Hi Reza,
>>
>> I’m not sure this is possible right now. I recently tried making a
>> service which would need the x display variable and I got stuck right
>> about when I needed the logged in user. I would love to see it though.
>>
>> Does anyone else know?
>
> I don't think there's an easy solution that's integrated into the Guix
> System (formerly known as GuixSD). Instead, the best approach is to use
> any of "the usual" methods for starting up user processes. For example,
> you might use the ~/.config/autostart convention:
>
> https://freedesktop.org/wiki/Specifications/autostart-spec/
>
> --
> Chris
next prev parent reply other threads:[~2019-02-09 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 15:16 User-Level services Reza Alizadeh Majd
2019-02-04 20:21 ` John Soo
2019-02-09 8:48 ` Chris Marusich
2019-02-09 13:14 ` John Soo [this message]
2019-02-09 17:34 ` nly
2019-02-09 22:25 ` John Soo
2019-02-10 18:23 ` Pierre Neidhardt
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=F7063773-FDB5-4422-B443-29393B466A5D@asu.edu \
--to=jsoo1@asu.edu \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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.