On Tue, Oct 20, 2020 at 02:53:50PM +0200, Oliver Schad wrote: > But because it could cause a production problem (think about a master > SQL server in a high traffic situation wich kills all his caches during > restart and maybe will be down for minutes), I think there should be a > way to give s6-rc some advice manually, how to handle that situation.
I did this in two steps (of course, both after first checking that the service runs correctly and that `s6-rc-update -n' outputs were right): * Add the new service, without declaring any dependencies on it; compile the service database, and run `s6-rc-update'. * `s6-rc -u change' the new service, then declare any dependency on the service; compile the database again, and run `s6-rc-update' again. -- My current OpenPGP key: RSA4096/0x227E8CAAB7AA186C (expires: 2022.09.20) 7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C