From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2381 Path: news.gmane.org!.POSTED!not-for-mail From: Guillermo Newsgroups: gmane.comp.sysutils.supervision.general Subject: s6-rc live state and database format upgrades Date: Sun, 20 May 2018 16:53:39 -0300 Message-ID: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1526845895 26914 195.159.176.226 (20 May 2018 19:51:35 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 20 May 2018 19:51:35 +0000 (UTC) To: supervision@list.skarnet.org Original-X-From: supervision-return-1972-gcsg-supervision=m.gmane.org@list.skarnet.org Sun May 20 21:51:31 2018 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1fKUMc-0006tz-Dj for gcsg-supervision@m.gmane.org; Sun, 20 May 2018 21:51:30 +0200 Original-Received: (qmail 6120 invoked by uid 89); 20 May 2018 19:54:08 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 6113 invoked from network); 20 May 2018 19:54:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=THlwtGyjND+KJo09E68+5HWOH3brhDmLiKWwr9DTm+I=; b=LVqAHWdQ6nzQSPcdKg26pbSHpv2sh/x4UBPq4CHE4G2BNNtFsyPmJq17GLOR1sx/mu xRSYJyBskjz+tbrnZg6S2xbqKfEsFxacrtoccIoktJ5dhAKEcjnKa/mp2I3M4gl0jQ41 3GauqWc/7rSZg/USQcCnRxf+zkGlGD/jsuHUWZg6JufN8tvoSDKTT6Yto/+iizqz4ZeJ Qt0PHzgik5+qiA7caNu9YqLfBkRLGxinQwYcJ4PW+WSECRl8RixrRhio9SLu0FolsP2/ PXULwoTwHCN1MQNK9LWd5Osj+Yb1ggQ40iwK1cpLtXUeoBE625z4ES0Pdu17k8Dvylo4 LmjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=THlwtGyjND+KJo09E68+5HWOH3brhDmLiKWwr9DTm+I=; b=FjOVxYGwytUbqiRMyeXkeJq7mCum+QfxoEsK3cPAUchzuqRe7zcergw85GQpmKSF+d br4p2Nmcr4B1xDHeiB4E4kHDboubflYhSsfu9AA24nRx7aXSI3n3Cuw6BdGp0nPIqg9O Hn0KZMiOL8RDFE9agyhykqrtGVra6+2IaW34mLrp0uSlV3UPBwzYtS0CwzhHm1omJmSj o0W+e0gqlOikYPMIh+xeLAX0iYHKXIHs1NPN9lamShOv1vRLcOc17zoL25QY+FFGBVN0 LZqHWXSrGn58SJuOM2f2EpG0E+yHEONuqvFfh9zRCkDExsCNCO9CyVvjFVjTBMDX7KuI Zz4A== X-Gm-Message-State: ALKqPwetkXpJalMRNdUfMLNPHThiWodS60fAm1YGbDDaMG3Iy+f+N8Q0 Bx09C0knmaMhGxOBRZYclOOOb63nsdhZEyKEcM8= X-Google-Smtp-Source: AB8JxZolNDBifRDws+dICWMYLA81neEew0popN3Lop2Yuw8TXhXP9slFH3HRGVxCJV7vlltju3eO7ixfywSIqsmCIX4= X-Received: by 2002:a6b:954c:: with SMTP id x73-v6mr18298365iod.225.1526846019565; Sun, 20 May 2018 12:53:39 -0700 (PDT) Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2381 Archived-At: 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.