diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2017-09-30 13:14:20 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2017-09-30 13:14:20 +0000 |
| commit | c06c68253b90670ca66f22be40ffbd198f22145f (patch) | |
| tree | fc7608cb35b5164854e42494f7dbd2f99c73b6ce /doc/s6-rc-update.html | |
| parent | f44565234a719600bbd8dc66308bc7be2683a8a6 (diff) | |
| download | s6-rc-c06c68253b90670ca66f22be40ffbd198f22145f.tar.xz | |
Add doc precisions about live compiled dbs
Diffstat (limited to 'doc/s6-rc-update.html')
| -rw-r--r-- | doc/s6-rc-update.html | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html index 6c23975..178d299 100644 --- a/doc/s6-rc-update.html +++ b/doc/s6-rc-update.html @@ -272,6 +272,11 @@ old compiled unless more work is performed. It is recommended to keep a <a href="s6-rc-init.html">s6-rc-init</a> on <tt>current</tt>, and to make <tt>current</tt> a link to the new compiled right after a s6-rc-update invocation. </li> + <li> s6-rc-update is the only way to "free" the old compiled database +for displacement or deletion. A live compiled database must not be +tampered with. After a s6-rc-update invocation, the old database isn't +live anymore and can be moved or deleted; instead, <em>newdb</em> is +live. </li> </ul> </body> |