Re: misc/17328 (rc.local is called in alphabetical order, not at the (nearly) end of rc process)

[kre%NetBSD.org@localhost]

Synopsis: rc.local is called in alphabetical order, not at the (nearly) end of rc process

State-Changed-From-To: open->closed
State-Changed-By: kre%NetBSD.org@localhost
State-Changed-When: Fri, 17 Jun 2022 05:02:31 +0000
State-Changed-Why:
Closing this 20 year old PR, there is no good solution to deciding
when rc.local should be run - ordering depends upon what is being
done, and by its very definition, rc.local does site-dependent things.
When those should be run cannot possibly be centrally planned.

My personal opinion is that rc.local is a waste of time - though it is
trivial to use - and that sites should simply make, and install,
suitable rc.d scripts for anything they want to have run at startup
time, in which case they can be placed into the ordering scheme in
whatever place is appropriate (which isn't necessarily the same for
all local startups - someone might have custom hardware which needs
firmware loaded very early in the boot sequence for example - the same
site might want to enable some features of that hardware operationally
only after logins are enabled - rc.local cannot do both).

This PR was clearly going nowhere.   It is now done.