Re: s6 instanced services are "forgotten" after s6-rc-update

From: Carlos Eduardo <>
Date: Wed, 8 Feb 2023 22:43:55 -0300

Am I missing something? Building the s6 git master gives:

src/libs6/s6_servicedir_instances_recreate_offline_tmp.c:26:9: error:
call to undeclared function 'sals'; ISO C99 and later do not support
implicit function declarations

`grep -R sals skalibs s6` (both being git master clones) only returns
the line mentioned in the error message.

Em qua., 8 de fev. de 2023 às 03:56, Laurent Bercot
<> escreveu:
> >On s6-instance-update, as a user I'd expect it to exist and be run
> >automatically as part of s6-rc-update. Since restarting applies the
> >new definition for longruns, having to do one extra step (or two if
> >s6-instance-update isn't made) per instance of a templated longrun
> >would be counterintuitive.
> It took a bit of creative juice, and significant refactoring, but I
> think I finally got it down.
> The current s6-rc git will remember your created instances from one
> compiled db to the next across s6-rc-update, no matter the state of the
> service at the time of the update.
> If the updated instanced service is live, then the new template will
> be copied to all the instances, but the instances will still be
> running on the old template until they're killed via
> s6-instance-control,
> at which point they will restart on the new template.
> This is in line with the principle of maximizing service uptime and
> waiting for admin input before killing processes.
> Please try it and tell me if it's working for you. You'll need to
> build against the latest git of skalibs and s6.
> --
> Laurent
Received on Thu Feb 09 2023 - 02:43:55 CET

This archive was generated by hypermail 2.4.0 : Thu Feb 09 2023 - 02:44:37 CET