public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] [report 6.25-7.4] Daemons in Gentoo Prefix with OpenRC (extended to improving to OpenRC)
Date: Mon, 9 Jul 2012 14:35:48 -0400	[thread overview]
Message-ID: <CAGfcS_=T4tty80PCD50sam3BsE38M+kVjUABcai-7Ft0FjVMGQ@mail.gmail.com> (raw)
In-Reply-To: <86a9z9qurj.fsf@gmail.com>

On Mon, Jul 9, 2012 at 3:05 AM,  <heroxbd@gmail.com> wrote:
> Luca Barbato <lu_zero@gentoo.org> writes:
>>> What we've discussed in the beginning, such as event-driven init,
>>> periodical events, process monitoring and crash restart are still on
>>> the todo list.
>>
>> That's great, do you feel confident you'll be able to get all of this
>> done?
>
> I feel these are not technically difficult. But the policies count,
> besides the debates that if we really need these fancy features for an
> init system. My current feeling (or planning) is that just to make dirty
> ones with simple scripts to see if our community (debian is more similar
> to us than fedora) really like the things. The rule of thumb is to
> always make them optional, hopefully independent, components.
>

As a certified member of the peanut gallery I can testify that process
monitoring and restarting would be a very nice feature to have.
Having this sort of capability in a chroot/prefix would probably
create a bunch of possibilities.  Tools for doing this exist, but they
are weak.

I switched a VM over to systemd because it had an unstable daemon and
I wanted to try out this feature.  Since systemd places each daemon in
a cgroup it is able to fairly effectively monitor what is going on
with them.  That might be something to keep in mind if you move ahead
with this.

I don't use a laptop with Gentoo so event-driven init is less useful
personally, but I imagine that if I had one it would be very nice to
have.  Again, I'd look at what upstart/systemd are doing to avoid
re-inventing the wheel here.

Keep in mind that process restarting is actually a very standard
feature in init - we just rarely actually run daemons directly from
init.  On the occasion that I've actually stuck something in inittab
init is very diligent in propping it back up.  The challenge will be
things like hung processes that don't actually die - but we can start
with the simple case.

Rich



  reply	other threads:[~2012-07-09 21:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  4:05 [gentoo-soc] [report 6.3-6.10] Daemons in Gentoo Prefix with OpenRC heroxbd
2012-06-11 17:05 ` Luca Barbato
2012-06-20 23:36   ` [gentoo-soc] [report 6.11-6.17] " heroxbd
2012-06-21  4:55     ` Luca Barbato
2012-06-21  7:13       ` heroxbd
2012-06-21  7:50         ` Luca Barbato
2012-06-26 23:25     ` [gentoo-soc] [report 6.18-6.24] Daemons in Gentoo Prefix with OpenRC (extended to improving to OpenRC) heroxbd
2012-07-04 15:31       ` [gentoo-soc] [report 6.25-7.4] " heroxbd
2012-07-04 16:34         ` Luca Barbato
2012-07-05 12:43           ` heroxbd
2012-07-05 13:21             ` Luca Barbato
2012-07-09  7:05               ` heroxbd
2012-07-09 18:35                 ` Rich Freeman [this message]
2012-07-09 19:11                   ` Luca Barbato

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='CAGfcS_=T4tty80PCD50sam3BsE38M+kVjUABcai-7Ft0FjVMGQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-soc@lists.gentoo.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