From 776c6ad7c4e24bdb5e039c088703f1fee9a2cfd8 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 23 Sep 2015 03:37:07 +0000 Subject: Some documentation updates --- doc/s6-rc-update.html | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) (limited to 'doc/s6-rc-update.html') diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html index fc049b4..1e56ba2 100644 --- a/doc/s6-rc-update.html +++ b/doc/s6-rc-update.html @@ -32,7 +32,7 @@ s6-rc-update will do its best on its own, but it lets the user give it instructions to handle difficult cases; and rather than implement doubtful heuristics, it will fail with an error message in -situations it really cannot solve. +situations it cannot solve.

Interface

@@ -254,13 +254,21 @@ be the same argument that was given to the booted. In other words: it should be the name of the symbolic link pointing to the real directory containing the live information, not the name of the real directory. -
  • The old compiled service database is left unchanged, and the new compiled +
  • If a longrun service is renamed from oldname to newname, +but not restarted, the +s6-supervise +process in charge of it will still show up in the process list as +s6-supervise oldname. This is purely cosmetic. To make +s6-supervise pick up the new name, make sure to restart the service when +invoking s6-rc-update.
    • +
  • After a s6-rc-update invocation, the old compiled service database +is left unchanged where it was, and the new compiled service database is used in-place. If the machine is rebooted, the s6-rc-init invocation will still boot on the old compiled unless more work is performed. It is recommended to keep a current symbolic link to the current compiled, to always s6-rc-init on current, and to -make current point to the new compiled right after a s6-rc-update +make current a link to the new compiled right after a s6-rc-update invocation.
    • -- cgit v1.2.3