I think I found a bug in the dynamic instance feature:
if the "run", "finish", "up" and "down" files in the initial template directory are not made executable, they will never become and s6-supervise will fail to execute them.
This happens when using s6-instance-maker to create an s6-rc service.I consider this a bug, since the same is not true for s6-rc source definitions. Whether those files are executable or not are executable in the source directories does not matter, they always end up executable in the scan directory.
Paul
OpenPGP_0x71C7C85A2EA30F62.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
