From: "Ludovic Courtès" <ludo@gnu.org>
To: rendaw <7e9wc56emjakcm@s.rendaw.me>
Cc: help-guix@gnu.org
Subject: Re: Services and log management/monitoring
Date: Fri, 19 Apr 2019 14:09:34 +0200 [thread overview]
Message-ID: <87imvaci2p.fsf@gnu.org> (raw)
In-Reply-To: <4428ea68-57fe-5459-0e26-529bc05d0b31@s.rendaw.me> (rendaw's message of "Fri, 19 Apr 2019 00:11:49 +0900")
Hi,
rendaw <7e9wc56emjakcm@s.rendaw.me> skribis:
> I think fundamentally what I'd most like to know is when should I use a
> Shepherd service vs a non-Shepherd service. Maybe it's as simple as: if
> you don't have any specific requirements always define a Shepherd service.
It’s hard to answer that question in the abstract. Do you have an
example in mind that we could work through?
> As a metaphor, maybe Shepherd services would be similar to the plain
> units in systemd.
Yes, I think so.
> Beyond what a service actually is though I have a few more questions:
>
> * Both
> https://www.gnu.org/software/guix/manual/en/html_node/Service-Composition.html
> and
> https://www.gnu.org/software/guix/manual/en/html_node/Shepherd-Services.html#Shepherd-Services
> appear to show a dependency graph.
The first page shows a service extension graph.
The second page shows a graph of dependencies among Shepherd services.
These are two different beasts.
> Are the dependency graphs Shepherd and non-Shepherd services
> entirely separate? Or maybe I'm completely misunderstanding
> "extension" in this context. Can an inet service depend on a non-inet
> service? Can an inet service depend on a d-bus service? * Is there a
> way to hook into service events - that is, run some code when a
> service starts or stops?
An inetd service cannot “depend” on a non-inetd service; a D-Bus service
cannot depend on a non-D-Bus service. Both D-Bus and inetd have their
own notion of what a service is, how to start it, etc., which is
separate from what the Shepherd does.
I reckon that calling everything a “service” does not help understand
all this…
HTH,
Ludo’.
next prev parent reply other threads:[~2019-04-19 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 18:12 Services and log management/monitoring rendaw
2019-04-17 21:20 ` Ludovic Courtès
2019-04-18 15:11 ` rendaw
2019-04-19 12:09 ` Ludovic Courtès [this message]
2019-04-19 15:47 ` rendaw
2019-05-04 7:01 ` Chris Marusich
2019-05-04 8:01 ` rendaw
2019-05-04 8:24 ` Chris Marusich
2019-05-04 8:32 ` rendaw
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=87imvaci2p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=7e9wc56emjakcm@s.rendaw.me \
--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.
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).