Harden daemon service installation
This commit is contained in:
parent
443602a30b
commit
678865bfdc
6 changed files with 784 additions and 46 deletions
|
|
@ -39,11 +39,16 @@ geth status
|
|||
```
|
||||
|
||||
`daemon install` initializes the selected home if needed, installs and enables
|
||||
a service for the current user, and starts it. It never installs a system
|
||||
service. Common lifecycle operations are direct:
|
||||
a service for the current user, starts it, and waits for local control to become
|
||||
ready. It never installs a system service. A binary launched from a Cargo target
|
||||
or temporary directory is copied into the selected geth home first, preventing
|
||||
later build cleanup from breaking the service. Common lifecycle operations are
|
||||
direct:
|
||||
|
||||
```sh
|
||||
geth daemon status
|
||||
geth daemon logs
|
||||
geth daemon logs --follow
|
||||
geth daemon stop
|
||||
geth daemon start
|
||||
geth daemon uninstall
|
||||
|
|
@ -53,6 +58,9 @@ The older `geth daemon service ...` family remains supported for scripts and
|
|||
advanced options. In particular, `geth daemon service install` installs without
|
||||
starting unless `--start` is supplied.
|
||||
|
||||
If readiness times out, inspect `geth daemon status` and `geth daemon logs`.
|
||||
Use `daemon install --no-wait` only when another process owns readiness checks.
|
||||
|
||||
### Keep state but run in the foreground
|
||||
|
||||
User story: as a developer, I want persistent state and logs attached to my
|
||||
|
|
|
|||
Loading…
Reference in a new issue