One property of OpenRC is it has no facility to respawn a daemon when the old daemon crashes. Some folks like it this way, some don't, but it's a fact of OpenRC. Except...
There are two ways to have OpenRC respawn. Way 1 is to run the daemon from /etc/inittab, with the "respawn" flag. Remember, OpenRC doesn't have its own PID1, and traditionally uses sysvinit's PID1. Way 2 is to have OpenRC run either runit or s6 from /etc/inittab with "respawn", and then to put all respawnable daemons in runit or s6. Running either runit or s6 *as a supervisor rather than an init* is dead-bang easy. Since about 2010 I've been doing something similar: I ran daemontools on top of sysvinit, and it always worked out great for me. SteveT On Mon, 14 May 2018 02:33:21 -0400 chill...@protonmail.com wrote: > Afaik openrc is compatible with the init scripts used by all > packages. Installing it and rebooting should be enough to start using > openrc. It worked OK for me when I tested it. > > This is probably possible on Jessie as well but I haven't tested that. > > Cheers, > > chillfan > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On May 14, 2018 1:52 AM, <wirelessd...@gmail.com> wrote: > > > I’ve read that the ascii RC has optional support for OpenRC. How > > can I switch to this on an existing system to try it out? > > > > Is it simply a matter of running “apt-get install openrc”? > > > > If I switch, will I have to create new service definition files for > > each existing daemon in /etc/init.d or can it read and reuse those > > files automatically? > > > > Are there any good tutorials out there on using it, aside from the > > Gentoo documentation? > > > > Thanks > > > > —Tom > > > > Dng mailing list > > > > Dng@lists.dyne.org > > > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
