On 9/23/20 7:49 PM, Dudemanguy via artix-general wrote:> "exec s6-rc
-bda change"
Wait, on second thought. Maybe this is the problem after all?
Checking the skarnet documentation:
>-b : blocking lock. If the service database is currently being used by
>another program, s6-rc will wait until that other program has released
>its lock on the database, then proceed. By default, s6-rc fails with an
>error message if the service database is currently in use. The default
>is the safe behaviour: for instance, it will correctly detect and fail
>nested s6-rc invocations (which are an admin error), whereas s6-rc -b
>would deadlock in such a case.
https://skarnet.org/software/s6-rc/s6-rc.html
Perhaps you somehow have a nest s6-rc invocation causing a deadlock?
That would explain it.
More information about the artix-general
mailing list