supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Guillermo <gdiazhartusch@gmail.com>
To: supervision@list.skarnet.org
Subject: s6-rc live state and database format upgrades
Date: Sun, 20 May 2018 16:53:39 -0300	[thread overview]
Message-ID: <CADQ2Nw9-A=UM5McwEELE+VN_0QAqr_B8vXY7gOm-Jvz=oCSK0A@mail.gmail.com> (raw)

Hello.

I was recently reviewing the instructions for the s6-rc dabatase
upgrade procedure, and they made me wonder what would happen if:

* s6-rc-format-upgrade was called with a compiled database that is not
the exact 0.4.0.x equivalent of the one currently associated with the
live state directory (i.e. other that a database created with
s6-rc-compile from version 0.4.0.x and the exact same service
definitions).

* s6-rc-update from version 0.4.0.x was called with a live state
directory currently associated with a <=0.3.0.0 database.

Is any of these things capable of trashing s6-rc's live state? I think
that the documentation is clear about the upgrade procedure, but that
these could be likely ways of accidentally screwing it up. Something
like the latter was actually the database upgrade procedure for
previous backwards-incompatible s6-rc upgrades, right? Although I
don't know if any of them involved a database format change.

Also, I'm lost about the role of version 0.3.0.1:

* https://www.mail-archive.com/skaware@list.skarnet.org/msg01096.html
* https://git.skarnet.org/cgi-bin/cgit.cgi/s6-rc/tree/doc/upgrade.html?h=real_0.3.0.1

Development of 0.3.0.1 was done in the skarnet.org Git repository in a
'real_0.3.0.1' branch. Development of 0.4.0.0 was done in the master
branch, and the current upgrade notes don't even mention 0.3.0.1:

* http://www.skarnet.org/software/s6-rc/upgrade.html

So, in the end, does upgrading from 0.3.0.0 to 0.4.0.x require an
intermediate 0.3.0.1 s6-rc-compile + s6-rc-update step, and then
0.4.0.x s6-rc-compile + s6-rc-format-upgrade, or not?

(I didn't have running services that I had to preserve, so personally
I didn't need any special care and just upgraded from whatever I had
at the time to s6-rc-0.4.0.0, but s6-rc-format-upgrade is now there
and one might need to explain or remind correct usage :) )

Thanks,
G.


             reply	other threads:[~2018-05-20 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-20 19:53 Guillermo [this message]
2018-05-20 23:01 ` Laurent Bercot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADQ2Nw9-A=UM5McwEELE+VN_0QAqr_B8vXY7gOm-Jvz=oCSK0A@mail.gmail.com' \
    --to=gdiazhartusch@gmail.com \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).