From 85e2821400dafd4afc4b75da331d2fd2129c5238 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 4 Dec 2017 18:11:24 +0000 Subject: Add s6-rc-format-upgrade --- doc/s6-rc-format-upgrade.html | 125 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) create mode 100644 doc/s6-rc-format-upgrade.html (limited to 'doc/s6-rc-format-upgrade.html') diff --git a/doc/s6-rc-format-upgrade.html b/doc/s6-rc-format-upgrade.html new file mode 100644 index 0000000..1b11e39 --- /dev/null +++ b/doc/s6-rc-format-upgrade.html @@ -0,0 +1,125 @@ + + + + + + s6-rc: the s6-rc-format-upgrade program + + + + + + +

+s6-rc
+Software
+skarnet.org +

+ +

The s6-rc-format-upgrade program

+ +

+ s6-rc-format-upgrade is a program that is normally used +very rarely: when the s6-rc package is upgraded, some +services are currently managed with s6-rc, and the database +format has changed. This program transitions a live directory +using a database with the old s6-rc format (the one being +replaced) so that it uses a database with the new s6-rc format. +

+ +

+ The point is to ensure a smooth transition between different +versions of s6-rc without needing a reboot. +

+ +

+ s6-rc-format-upgrade is very different from +s6-rc-update and does not +duplicate its functionality: +

+ + + +

Interface

+ +
+     s6-rc-format-upgrade [ -v verbosity ] [ -l live ] [ -t timeout ] [ -b ] newcompiled
+
+ + + +

Options

+ + + +

Typical usage

+ +

+ s6-rc-format-upgrade is only necessary when the database format +changes, which only happens when s6-rc's major version number +(the third number from the right) changes. The correct order of +operations is then the following: +

+ + + + + -- cgit v1.2.3