1 files changed, 46 insertions, 0 deletions
diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html
new file mode 100644
index 0000000..26ebf48
--- /dev/null
+++ b/doc/s6-rc-update.html
@@ -0,0 +1,46 @@
+<html>
+  <head>
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+    <meta http-equiv="Content-Language" content="en" />
+    <title>s6-rc: the s6-rc-update program</title>
+    <meta name="Description" content="s6-rc: the s6-rc-update program" />
+    <meta name="Keywords" content="s6-rc command rc update s6-rc-update init dependency state management services" />
+    <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> -->
+  </head>
+<body>
+
+<p>
+<a href="index.html">s6-rc</a><br />
+<a href="http://skarnet.org/software/">Software</a><br />
+<a href="http://skarnet.org/">skarnet.org</a>
+</p>
+
+<h1> The s6-rc-update program </h1>
+
+<p>
+ s6-rc-update is an <em>online service database switcher</em>:
+it will replace your compiled service database with another
+one, and adjust the live state accordingly.
+</p>
+
+<p>
+ Live upgrading a service database is no small feat, and no
+fully automated system can get it right in all cases.
+s6-rc-update will do its best on its own, but it lets you
+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.
+</p>
+
+<h2> Interface </h2>
+
+<pre>
+     s6-rc-update [ -v <em>verbosity</em> ]
+</pre>
+
+<h2> Options </h2>
+
+</body>
+</html>