unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: One-shot Shepherd services
Date: Tue, 30 Apr 2019 19:24:23 +0200	[thread overview]
Message-ID: <CAE4v=phfx06PFBJcKbAZPKniGBHhKacvWOA5EbbyR0qgw4R1+g@mail.gmail.com> (raw)
In-Reply-To: <878svrlggj.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

Hello,

Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2019. ápr. 30., K, 16:24):

> Chris Marusich <cmmarusich@gmail.com> skribis:
>
> > At first I was a little confused about why we would ever want to use a
> > one-shot shepherd service instead of an activation snippet, but after
> > reviewing the account-shepherd-service, I think I understand.  It seems
> > that we make it a one-shot shepherd service instead of an activation
> > snippet so that we can take advantage of shepherd's service dependency
> > management.  In the case of account-shepherd-service, it looks like we
> > made it a shepherd service to ensure that it would run after
> > 'file-systems' is up.  This makes sense, since it could be a little
> > awkward to try to ensure proper execution order by extending the
> > activation service, and even if we did that, it would duplicate the
> > dependency management logic that shepherd gives us already.
>
> Yes, that’s exactly the reason.
>
>
This raises the question, if we are willing to convert some more activation
snippets to one-shot services. Are there any candidates for that?


> The ‘user-homes’ service was introduced to fix a bug whereby, if you
> were using a separate /home, home directories would be created at the
> wrong time—i.e., before the real /home was mounted.
>
> Ludo’.
>
>
Best regards,
g_bor

[-- Attachment #2: Type: text/html, Size: 2054 bytes --]

  reply	other threads:[~2019-04-30 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 21:38 One-shot Shepherd services Ludovic Courtès
2019-04-19  4:09 ` znavko
2019-04-19  8:36   ` Ludovic Courtès
2019-04-19  6:40 ` Pierre Neidhardt
2019-04-19 15:02   ` User Services Joshua Branson
2019-04-19 15:33     ` Pierre Neidhardt
2019-04-30  3:33 ` One-shot Shepherd services Chris Marusich
2019-04-30 14:23   ` Ludovic Courtès
2019-04-30 17:24     ` Gábor Boskovits [this message]
2019-05-03 13:53       ` Ludovic Courtès
2019-05-04  5:52         ` Chris Marusich
2019-05-03 19:15 ` Thompson, David

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='CAE4v=phfx06PFBJcKbAZPKniGBHhKacvWOA5EbbyR0qgw4R1+g@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).