Re: [gentoo-soc] (draft) final report for OpenRC soc project 2012

Dear Luca,

heroxbd@×××××.com writes:

>>> 4. OOM killer/periodical command
>>>
>>>     Not implemented here, tested with monit (http://mmonit.com/monit/)
>>>     and fcron (http://fcron.free.fr/). No integration or modification is
>>>     need in OpenRC, unlike runit. At most, we can introduce a
>>>     IN_PERIODICAL envvar, as how IN_HOTPLUG works.
>>
>> I'd like to have more information here.
>
> Got it, preparing...

For monitoring against OOM http://wiki.gentoo.org/wiki/Monit

cron/at is too general to document, there is one at

  http://www.gentoo.org/doc/en/cron-guide.xml

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.
  
>>> 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


>>> Succeeded, thinking of documenting it in wiki.
>
> Got it.

Together with stacked runlevel.

  http://wiki.gentoo.org/wiki/OpenRC/StackedRunlevel

Cheers,
Benda