Can you explain the essence of how the code evaluates "script does useful work"?
The obvious way to put it is "is the effect on the system (other than cpu time, filesystem reads, effects on caches) from running this script the same as the effect of not running it"? If there is a rule that each script must have a yes/no variable controlling actions, then I can see this optimization. Or really, skipping any script that does have a variable. But, rc.d scripts sort of seem like arbitrary shell commands. I therefore wonder if we have rules for rc.d scripts that enable this kind of optimization, or if some subset of optimizable rc.d scripts are recognized. How does this interact with rc.d scripts from pkgsrc or elsewhere, that do not necessarily follow rules? (Also, it seems obvious that if you commit this, it should default to off at first, except perhaps for particularly slow arches.)
