Re: Some suggestions on old-fashioned usage with s6 2.10.x

> major version upgrades may break things. As plain as day. > I prefer a short, sharp pain (when things break) followed by > relief (when they're fixed) to a long dull ache (maintaining > compat code). I could not agree more, it would also bring zero anyhow except than extra, likely convoluted,

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 05:21:59PM +, Laurent Bercot wrote: > There is no really good solution, and I prefer a short, sharp pain > (when things break) followed by relief (when they're fixed) to a long > dull ache (maintaining compat code). I see. I personally prefer to retain compat code if

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 06:08:36PM +0800, Casper Ti. Vector wrote: > then move the `s6-svc -X' invocation from `rc.halt' into `rc.fin' The `s6-svc -a' invocation in `rc.halt' needs to be moved accordingly. Moreover, `.s6-svscan/finish' (linked to `rc.halt') will still need its $1 set to `reboot',

Some suggestions on old-fashioned usage with s6 2.10.x

I did not actively follow the recent evolution of s6, and have just been bitten badly by s6 2.10.x on my Alpine servers (where slew [1] is used of course) when it comes along with other updates. [1] First, kernel panic on booting. With some tentative

s6 supervision

Hi Team, Is there an API/ command in s6 code to get the information of a process and its pid by giving the service name that has started the process? And does s6-svscan/s6-supervise have the knowledge of service-name& process name & process pid so that it can be fetched to another process using

Re: Some suggestions on old-fashioned usage with s6 2.10.x

BTW, seems to be returning empty HTTP replies now; both and work as expected though. That is a side effect of a recent s6-networking addition, where s6-tlsd passes the SNI server name to the application via an

Re: Some suggestions on old-fashioned usage with s6 2.10.x

El jue, 28 ene 2021 a las 7:08, Casper Ti. Vector escribió: > > I did not actively follow the recent evolution of s6, and have just been > bitten badly by s6 2.10.x on my Alpine servers (where slew [1] is used > of course) when it comes along with other updates. > > [1]

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Fri, Jan 29, 2021 at 12:07:11AM +, Laurent Bercot wrote: > I may change it back, but I don't think the current state is broken, > because you're not supposed to access git.skarnet.org via HTTP(S)! :P Actually I do visit the CGit web interface fairly often, using it as a poor man's GitHub

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 10:41:24PM -0300, Guillermo wrote: > Out of curiosity, do you have a reason for wanting to keep the > "old-fashioned way"? Is it a goal of your project to depend on s6 and > s6-rc, but not current s6-linux-init? It seems to me that doing so > would be easier. It even looks

Re: Some suggestions on old-fashioned usage with s6 2.10.x

I did not actively follow the recent evolution of s6, and have just been bitten badly by s6 2.10.x on my Alpine servers (where slew [1] is used of course) when it comes along with other updates. Sorry. This bears repeating: major version upgrades may break things. Compatibility is a good

Re: Some suggestions on old-fashioned usage with s6 2.10.x

On Thu, Jan 28, 2021 at 07:09:08PM +0800, Casper Ti. Vector wrote: > Moreover, `.s6-svscan/finish' (linked to `rc.halt') will still need its > $1 set to `reboot', `halt' or `poweroff' by `s6-svscan' on exec(). I did not realise the great simplification to the command line options of