You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... or at least make it configurable. Many embedded systems use this feature to extend,
or even live-patch systems between major upgrades of firmware. Security wise it is a
good thing to at least show on the console what scripts are executed outside the normal
bootstrap path.
The text was updated successfully, but these errors were encountered:
@troglobit For rc.local I don't think there's much more we can do since execution of the script is handed over to whatever is in the shebang in rc.local. All we can do is show on the console that rc.local is called, and that's already implemented.
For the runparts part, i guess some output like this would suffice:
[ STATUS ] Calling /rc.d/0001-foo
[ STATUS ] Calling /rc.d/0002-bar
Printing the progress of run-parts script just like for `rc.local`
seems reasonable. Also log a warning if any script exits abnormally.
Signed-off-by: Jacques de Laval <jacques@de-laval.se>
... or at least make it configurable. Many embedded systems use this feature to extend,
or even live-patch systems between major upgrades of firmware. Security wise it is a
good thing to at least show on the console what scripts are executed outside the normal
bootstrap path.
The text was updated successfully, but these errors were encountered: