nosh init system

[Adam]

On Sat, Feb 9, 2019 at 11:57 AM Enji Cooper <yaneurabeya at gmail.com> wrote:

> On Feb 9, 2019, at 09:32, Wojciech Puchar <wojtek at puchar.net> wrote:
>
> >> pid 2 and reap zombies.  We're missing a half-decent service
> >> management system.  On Linux, systemd performs both roles.  On
> >> FreeBSD, init(8) serves one role, and rc(8) is a tiny subset of a real
> >> service management system like systemd.
> >
> > systemd is overcomplex crap. And a reason many people migrated to
> FreeBSD from linux.
> >
> >>
> >> (I think the piece we would consider replacing or supplementing would
> >> be rc(8).  Part of that might be migrating some responsibilities from
> >> pid 1 to pid 2, such as spawning gettys.  I don't hold strong opinions
> >> about that.)
> >
> > this make sense but with spawning gettys left to init.
> >
> >
> > what do you want to improve in rc? starting services in parallel doesn't
> seem to be major problem to make i think.
>
> Starting and stopping services based on logical events and “run levels”,
> apart from what devd handles with hardware events is what comes to mind for
> me.
>
> rc(8) is also incredibly fragile when it comes to starting or stopping
> services beyond first boot, or when dealing with “optional” services, like
> nis/yp. I tried to clean this up a few years ago, but it’s not close to my
> ideal design (it feels like  a bubblegum and duct tape solution).
>

"incredibly fragile" indicates there is some common, easily triggered issue
with it.  Can you elaborate please?  I stop and restart base services and
others on a regular basis and don't see an issue there although I also
haven't use NIS for some time.
-- 
Adam