From 0a0aa75f06da164a37fe6ed7929029d76e978355 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 23 Feb 2026 08:58:12 +0000 Subject: doc typo fixes --- doc/s6-rc-set-install.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/s6-rc-set-install.html') diff --git a/doc/s6-rc-set-install.html b/doc/s6-rc-set-install.html index a9fb281..9c4d940 100644 --- a/doc/s6-rc-set-install.html +++ b/doc/s6-rc-set-install.html @@ -40,7 +40,7 @@ has been committed and that no changes have o
  • It takes the corresponding service database and copies it to the same directory as bootdb.
  • It calls s6-rc-update on that copy of the compiled service database, which makes it the new live database. Some services may be stopped, and -other started, in the process.
  • +others started, in the process.
  • It updates the bootdb link to point to the new database, so that next boot uses it.
  • @@ -78,12 +78,12 @@ a conversion file, which should be correct in most cases.
    -b, --block
    Pass the -b option to s6-rc-update, which makes it block rather than fail when the live database is currently being -used by another program - typically when an s6-rc change +used by another program — typically when an s6-rc change transition is under way.
    -K, --keep-old
    If this option is given, the old live database, after it has been -replaced, is kapt around, and s6-rc-set-install prints a line to stdout that +replaced, is kept around, and s6-rc-set-install prints a line to stdout that is the path to that old database. It can e.g. be used by automation to keep the possibility of rollbacks. By default, s6-rc-set-install will delete the old live database after -- cgit v1.3.1