Hello Laurent,
Thanks for your answers. Other opinions/experience welcome.
> That is a fair point. Normally, you should adjust the s6-rc
> timeouts (both the global one and the service-specific one) to
> make sure s6-rc does *not* time out before the service is ready -
> but if there's an
Hello all,
I am facing questions regarding the way to correctly handle
transition failures with s6-rc. The new permanent failure feature
already clarifies some scenarios but I still have doubts about
some cases. Below are two concrete examples. I would
be happy to have remarks or suggestions
Hello all,
After upgrading to the below release of skarnet packages, my system
is not booting anymore on MIPS. I am using buildroot and the
s6-linux-init-skeleton
provided there by Éric Le Bihan.
The init usually stays blocked there:
s6-rc: info: processing service fdholder: starting
with
> Doesn't
>
>svc -wD -T1000 servicedir || svc -k servicedir
>
> do what you want for the "hangup problem" ?
Problem is that you can't trigger that from s6-rc.
Lionel
What I would like to have is "s6-rc -d change foo" sending SIGTERM and then
SIGKILL if the service is not down after x seconds. Currently If a daemon hangs
it has annoying side effects. If I don't put a timeout on the s6-rc command
the state machine is blocked, and I cannot shut down the system
