summaryrefslogtreecommitdiff
path: root/doc/s6-rc-update.html
blob: fda6885677acd882dda4d5c718d3b22f1a21b794 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
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>

<p>
 To be written. s6-rc-update is currently the missing piece in the
s6-rc suite, which is the reason why s6-rc has not been officially released
yet. :-)
</p>

</body>
</html>