diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2026-10-17 04:10:16 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2026-10-17 04:10:16 +0000 |
| commit | 6ada80ed7e45ed630e4d9877a9b11e2dfddb4758 (patch) | |
| tree | 61d28af958e9922d1a2380b42b8137a0ac64be51 /examples/source-router/taiclockd-6-bis/run | |
| parent | db3fb428599c9c8fe105dcf4ba8d1c914c54cc26 (diff) | |
| download | s6-rc-6ada80ed7e45ed630e4d9877a9b11e2dfddb4758.tar.gz | |
Third part of the format-upgrade inclusion: add support in s6-rc-set-install
Now that everything is in place, we go for the main thing: add
snapshot support to s6-rc-set install. The workflow is:
- check the major version of the old db against the current s6-rc
- if the old db is up to date, nothing changes
- otherwise:
+ find the snapshot corresponding to the old db
+ compile it
+ copy the snapshot db to the bootdir
+ call s6-rc-format-upgrade on it
+ atomically switch the bootdb to it. At this point the snapshot
is the new bootdb: same as the old db, but with the correct major version.
+ unconditionally remove the old db
+ and now we can perform the regular s6-rc-update with the
wanted set, since they have the same major.
We also add --no-snapshot options to s6-rc-set-commit and
s6-rc-set-install, and propagate them in the supporting functions,
so users can manually skip all this bloat (and this is important
for the initial install).
All that remains is cleaning up obsolete snapshots. This will
probably go at the end of s6-rc-set-install as well.
Diffstat (limited to 'examples/source-router/taiclockd-6-bis/run')
0 files changed, 0 insertions, 0 deletions
