summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2018-10-30 22:02:28 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2018-10-30 22:02:28 +0000
commitfb6fdf5f24ee6921a1ba2651a534887de2e16fbc (patch)
tree20b09543d115077249c712f1f3a2370f58523915 /doc
parent159ac071aa6d2642d43e1ffc00c8fc818b057979 (diff)
downloads6-rc-fb6fdf5f24ee6921a1ba2651a534887de2e16fbc.tar.xz
Link a FAQ entry in s6-rc-update's doc (thanks danyspin97)
Diffstat (limited to 'doc')
-rw-r--r--doc/s6-rc-update.html18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html
index 178d299..0602d50 100644
--- a/doc/s6-rc-update.html
+++ b/doc/s6-rc-update.html
@@ -247,6 +247,24 @@ restart. </li>
<li> It will rename <tt>sqld</tt> to <tt>mysqld</tt> and make it restart.
</ul>
+<h2> Safely managing and updating compiled databases </h2>
+
+<p>
+ The sequence of operations needed to update a database from source to live
+can be a little tricky. It involves:
+</p>
+
+<ul>
+ <li> Compiling the new database without overwriting the live one </li>
+ <li> Calling s6-rc-update to safely replace the live database </li>
+ <li> Making sure the new database will be correctly used at boot time </li>
+</ul>
+
+<p>
+ <a href="https://skarnet.org/software/s6-rc/faq.html#compiledmanagement">This
+FAQ entry</a> gives a step-by-step explanation on how to proceed.
+</p>
+
<h2> Notes </h2>
<ul>