From: Wayne Marshall <wcm@b0llix.net>
To: Laurent Bercot <ska-supervision@skarnet.org>
Cc: supervision@list.skarnet.org
Subject: Re: [announce] perp-2.03: persistent process supervision
Date: Mon, 14 Mar 2011 15:02:25 +0100 [thread overview]
Message-ID: <20110314150225.7cf61c3c@b0llix.net> (raw)
In-Reply-To: <20110314131706.GA17316@skarnet.org>
Hi Laurent,
> I just have a question about your design:
>
> > * easy configuration: in place service activation and no
> > symlinks!
>
> Does that mean that perpd stores all the service states in
> memory ? To control or check on services, perpctl and other
> utilities connect to perpd via the Unix domain socket, right ?
Yes.
> So... the dreaded question... what happens if perpd dies ?
> Will perpboot restore a sane supervision tree ?
>
Yes.
First, perpd(8) won't die :)
If perpd(8) receives SIGTERM, it runs a controlled shutdown of
all services under its supervision, and then terminates itself.
Under normal (default) configurations, whenever perpd(8)
terminates it is restarted by either perpboot(8), or init(8) with
a "respawn" configuration in inittab(5). perpd(8) then
restarts all services marked for activation in /etc/perp.
Wayne
next prev parent reply other threads:[~2011-03-14 14:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 10:39 Wayne Marshall
2011-03-14 13:17 ` Laurent Bercot
2011-03-14 14:02 ` Wayne Marshall [this message]
2011-03-14 14:23 ` Robin Bowes
2011-03-14 14:34 ` Wayne Marshall
2011-03-14 16:47 ` Laurent Bercot
2011-03-14 17:39 ` Wayne Marshall
2011-03-14 17:52 ` Paul Jarc
2011-03-14 18:43 ` Wayne Marshall
2011-03-14 18:34 ` Laurent Bercot
2011-03-14 15:03 ` Charlie Brady
2011-03-14 15:35 ` Wayne Marshall
2011-03-14 17:02 ` Laurent Bercot
2011-03-14 17:42 ` Charlie Brady
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=20110314150225.7cf61c3c@b0llix.net \
--to=wcm@b0llix.net \
--cc=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.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 NNTP newsgroup(s).