Date: Sat, 13 Apr 2019 13:58:55 +0200
From: tlaro...@polynum.com
Message-ID: <20190413115855.ga1...@polynum.com>
| The question was more: why is it not the very last thing invoked?
An equally valid question would be why not the first? Or the last before
logins are enabled, or ...
The problem is that no-one (except you) knows what local is supposed
to do, that's its point. There is no place in the sequence where it
can be put where it will work for everyone.
IMO it would be better to delete it completely, writing an rc.d script
is not difficult (copyinmg an existing one and changing stuff is even
easier). It is only retained because of the long standing convention of
there being an /etc/rc.local in BSD, as more or less useless as that always
was.
Forcing it to be last makes it work for one category of uses, while being
useless for others. The same for any other position (but the earlier it
runs the more flexible, as what is in rc.local can always just delay
until something else is ready - whereas I don't know of a way to make
a late running rc.local force commands to run ahead of others that have
already completed).
kre
