On Thu, Jan 28, 2021 at 05:21:59PM +0000, 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 said code is so small that it can hardly be incorrect, especially when the breakage (like kernel panics) can be very severe. Arguably a major stylistic difference. > You seem to have found the proper way of managing this with SIG files, > but just in case: "s6-svscanctl -tb" will net you the old behaviour. Now I see; thanks. I also realised that the revised `s6-svc -X' proposal would result in wrong behaviour when there exists a `./finish' script, because the supervisor would exit early (and prematurely). BTW, <https://git.skarnet.org/> seems to be returning empty HTTP replies now; both <https://skarnet.org/> and <http://git.skarnet.org/> work as expected though. -- My current OpenPGP key: RSA4096/0x227E8CAAB7AA186C (expires: 2022.09.20) 7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C
