From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] (draft) final report for OpenRC soc project 2012
Date: Tue, 21 Aug 2012 17:55:30 +0200 [thread overview]
Message-ID: <5033AF72.2000101@gentoo.org> (raw)
In-Reply-To: <86sjbgpcd1.fsf@gmail.com>
On 8/21/12 4:07 PM, heroxbd@gmail.com wrote:
> For monitoring against OOM http://wiki.gentoo.org/wiki/Monit
So monit could be integrated in openrc easily ?
> cron/at is too general to document, there is one at
>
> http://www.gentoo.org/doc/en/cron-guide.xml
Agreed.
> upstart is designed to replace cron
>
> http://upstart.ubuntu.com/wiki/ReplaceCron
>
> systemd recommends to replace cron
>
> http://freedesktop.org/wiki/Software/systemd/Optimizations
>
> while OpenRC just work with it. For some fancy new feature to be used on
> non-servers, like "run every 5 minutes after start up", fcron can be
> used.
Not sure exactly what should we add here.
>>>> 5. event driven actions
>>>>
>>>> Same as hotplug feature already in OpenRC, triggered by udev, just
>>>> lack of documentation. If used with runlevel stacking (another under
>>>> documented feature of OpenRC), it can cover all the use cases I could
>>>> imagine.
>>>>
>>>> That's enough. upstart features a udev-upstart-bridge after all. It
>>>> is a cool feature and we can adopt it with a combo of tools and
>>>> achieve sane default behavior by packaging with, e.g., our beloved
>>>> ebuild. The revolutionary event based init design is more of
>>>> propaganding, IMHO.
>>>
>>> I'd like to see a wiki page or some more on that =)
>>
>> Got it, underway...
>
> A stub page is below. Still thinking of how to present it. May be we can
> just load it with examples which covers all the cases upstart being
> proud of.
>
> http://wiki.gentoo.org/wiki/OpenRC/Event_Driven
Yes, might be a good approach.
> http://wiki.gentoo.org/wiki/OpenRC/StackedRunlevel
Interesting example
lu
next prev parent reply other threads:[~2012-08-21 18:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 8:58 [gentoo-soc] report 7.16-7.23: improving OpenRC heroxbd
2012-08-07 4:53 ` [gentoo-soc] report 7.24-8.7: " heroxbd
2012-08-07 9:16 ` Luca Barbato
2012-08-08 23:24 ` [gentoo-soc] report 8.8: " heroxbd
2012-08-09 6:05 ` Luca Barbato
2012-08-10 2:56 ` [gentoo-soc] report 8.9: " heroxbd
2012-08-10 8:51 ` Luca Barbato
2012-08-11 0:31 ` [gentoo-soc] report 8.10: " heroxbd
2012-08-11 23:50 ` [gentoo-soc] report 8.11: " heroxbd
2012-08-13 8:33 ` Luca Barbato
2012-08-15 15:14 ` [gentoo-soc] (draft) final report for OpenRC soc project 2012 heroxbd
2012-08-15 21:47 ` Luca Barbato
2012-08-16 8:38 ` heroxbd
2012-08-16 11:41 ` Rich Freeman
2012-08-17 5:39 ` heroxbd
2012-08-17 7:29 ` Luca Barbato
2012-08-17 11:56 ` Rich Freeman
2012-08-20 3:04 ` heroxbd
2012-08-20 8:16 ` Luca Barbato
2012-08-20 10:25 ` Fabian Groffen
2012-08-20 16:32 ` Luca Barbato
2012-08-20 18:25 ` Fabian Groffen
2012-08-20 10:47 ` Rich Freeman
2012-08-20 16:34 ` Luca Barbato
2012-08-20 18:12 ` Rich Freeman
2012-08-20 18:28 ` Luca Barbato
2012-08-20 16:15 ` EBo
2012-08-21 14:07 ` heroxbd
2012-08-21 15:55 ` Luca Barbato [this message]
2012-08-22 2:04 ` heroxbd
2012-08-22 7:35 ` Luca Barbato
2012-08-27 10:46 ` Patrick Lauer
2012-08-27 12:37 ` Rich Freeman
2012-08-27 13:29 ` Luca Barbato
2012-08-27 14:10 ` Rich Freeman
2012-08-27 14:35 ` 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=5033AF72.2000101@gentoo.org \
--to=lu_zero@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