pub fn service_launch_arguments(cli: &Cli) -> Vec<String>Expand description
Re-serialize whichever CLI flags were given to install into the argument list the SCM
should launch the executable with. The SCM always starts a service’s executable bare (no
interactive shell, no inherited environment beyond the system default – notably including
a different %APPDATA% than whichever user ran install interactively, since services
typically run under their own account), so an explicit --config an operator wants
applied every time the service starts must be baked into the registration itself rather
than relying on how the executable happened to be invoked once at install time – see
crate::cli’s module doc comment.