diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2018-06-17 00:52:05 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2018-06-17 00:52:05 +0000 |
| commit | 3ea0b28892de170c5de281529613531dfa15eaa8 (patch) | |
| tree | 1c9fec71fba9f9abcf56041b9fe126dea0cc08dd /doc/s6-svscan-1.html | |
| parent | 70586b4a4ae15e008ee0a86dcb42602cc87744df (diff) | |
| download | s6-3ea0b28892de170c5de281529613531dfa15eaa8.tar.xz | |
Doc clarification
Diffstat (limited to 'doc/s6-svscan-1.html')
| -rw-r--r-- | doc/s6-svscan-1.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/s6-svscan-1.html b/doc/s6-svscan-1.html index 1f589cd..441e996 100644 --- a/doc/s6-svscan-1.html +++ b/doc/s6-svscan-1.html @@ -190,7 +190,7 @@ one-time initialization, with a big advantage over the "init-stage1" process: s6-svscan is running, as well as a few vital services, and if something bad happens, there's a getty for the administrator to log on. No need to play fancy tricks with <tt>/dev/console</tt> anymore! Yes, -the theoretical separation in 3 stages is a bit more supple in practice: +the theoretical separation in 3 stages is a bit more flexible in practice: the "stage 2" process 1 can be already running when a part of the "stage 1" one-time tasks are still being run. </p> |