Just tested out s6-rc-update and it works! Mostly. This is with the
current git head at position 930c7fb
Things it did right:
Computed my bundle name change between compiled and compile-new.
Built a new /run/s6/rc directory
and re-linked /run/s6/rc to it
Moved all the files for the various s6-
On Sun, Sep 13, 2015 at 2:34 PM, Laurent Bercot wrote:
>
> I'm afraid there's no real solution to the stragglers problem, and the
> only safe approach is to keep everything mounted all the time and only
> perform the unmounts in stage 3 after everything else has been done and
> the processes have
On 13/09/2015 20:25, Colin Booth wrote:
My current issue is that I'm initially remounting my root filesystem
as r/w as one of the first steps for s6-rc, which means that if I'm
doing everything correctly, s6-rc attempts to remount root as
read-only as part of its shutdown.
Yeah, indeed, that w
> This is the right way to proceed:
> * First s6-rc -da change
> * Then s6-svscanctl -t /run/service
>
> I don't understand the issue you're having: why would your rw filesystem
> be set read-only before the services come down ?
> - Your non-root filesystems should be unmounted via the corresp
On 13/09/2015 09:08, Colin Booth wrote:
I've been digging into managing a system completely under s6 and I
can't seem to find the right time to run `s6-rc -da change'. Run it
before sending s6-svscan the shutdown/reboot/halt commands and can end
up with a situation where your read/write drive has
Hey there,
I've been digging into managing a system completely under s6 and I
can't seem to find the right time to run `s6-rc -da change'. Run it
before sending s6-svscan the shutdown/reboot/halt commands and can end
up with a situation where your read/write drive has been set read-only
before you
