Re: One-shot Shepherd services

["Gábor Boskovits" <boskovits@gmail.com>]

[-- 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 --]