3 ms·
There are plenty of things doing this at the operating system level, going back a quarter of a century. One of the earliest was the System Resource Controller
by JdeBP 10y ago
There are plenty of things doing this at the operating system level, going back a quarter of a century.
One of the earliest was the System Resource Controller in IBM AIX 3.2 in 1992. Later that same decade, in the BSD and Linux worlds, came Daniel J. Bernstein's daemontools. A whole family of toolsets grew from that design, including Bruce Guenter's daemontools-encore, Gerrit Pape's runit, Laurent Bercot's s6, Wayne Marshall's perp, Adam Sampson's freedt, and nosh. There are also upstart, Linux systemd, MacOS launchd, and the Solaris Service Management Facility.
* http://jdebp.eu./FGA/daemontools-family.html http://jdebp.eu./FGA/daemontools-family.html
- andrewchambers 10y agoDaemon tools most certainly does not do what im talking about. It does blind restarts of single processes, not coordinated restarts and killing of collections of services.
- JdeBP 10y agoYou are voicing a long-standing fallacy. One builds the coördination on top of the base service management. The runit and perp way is to include the dependencies as calls to "sv check"/"perpok" in the run programs. s6-rc gives one "bundles". nosh has a mechanism of targets and "wants"/"conflicts" relationships.