pub enum BinaryPath {
Current {
path: PathBuf,
},
Missing {
recorded: PathBuf,
},
NotExecutable {
recorded: PathBuf,
detail: String,
},
Diverged {
recorded: PathBuf,
registered: PathBuf,
},
}Expand description
What became of the absolute path install recorded.
05-infrastructure.md item 6 in one type. Three of the four variants are
errors, and service status reports them as errors rather than as health —
which is the whole point, because the npm case produces a service that looks
installed, is registered, and cannot start.
Variants§
Current
The recorded path is a file, and the service manager still starts it.
Missing
Nothing is at the recorded path.
This is the npm upgrade: npm i -g @ivan-murzak/runner-manager puts the binary under
the active Node installation’s global prefix, and switching Node versions
with nvm, fnm, or volta moves that prefix. The service is still
registered, still set to start at boot, and starts nothing.
NotExecutable
Something is at the recorded path, but it is not a file the service manager could start.
Diverged
The record and the service manager name different binaries.
Implementations§
Trait Implementations§
Source§impl Clone for BinaryPath
impl Clone for BinaryPath
Source§fn clone(&self) -> BinaryPath
fn clone(&self) -> BinaryPath
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more