Built-in ordering

From: Steve Litt <slitt_at_troubleshooters.com>
Date: Sun, 20 Sep 2015 12:26:13 -0400

Hi all,

It just occurred to me that built-in ordering could be as simple as
making the very first loop, on, for want of a better word, svscanboot,
search for a directory with a file called "mefirst". Upon encountering
that directory, it would execute that directory's run script, which
would perform all the down file kludges or other ordering mechanisms
that the individual user wants.

Of course, if one is going to do an initial dummy loop, one could also
look for a file called "order" in each, whose contents indicate a
number to be sorted in order to get the startup ordering of all
longruns and oneshots. But IMHO that would require *a lot* more change
to the supervisor than simply looking for the first "mefirst"
encountered (and it would be a user error to have more than one
directory with a "mefirst").

Of course, all this could be avoided the LittKit way and just run a
script depositing "down" files before running the supervisor. But the
LittKit way specifically defies Laurent's proposal that PID1 be able to
restart the supervisor (I think).


Steve Litt
August 2015 featured book: Troubleshooting: Just the Facts
Received on Sun Sep 20 2015 - 16:26:13 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:19 UTC