On Sat, 23 Aug 2014 00:59:13 +0100
Laurent Bercot <ska-skaware_at_skarnet.org> wrote:
> You are correct, and it is by design indeed, but not my design -
> it's simply Unix.
Thank you for your quick reply.
> As a very rough rule of thumb, execline blocks represent processes.
> A sequence of commands in the same block will run with the same PID;
> the environment set with s6-envdir will then propagate to the end
> of the block. A new process will be spawned to run an inner block,
> and it will inherit that environment. And when a block ends, the
> process dies, and the outer block, an ancestor, has no idea of the
> environment that was set in the inner block.
>
Excellent. This makes it very straight forward to script.
> There are many exceptions to the "block = process" rule
I will gradually get better at differentiating the exceptions, but
I am definitely starting to appreciate the execline / pathexec
methodology. It is taking some getting used to, but I can see that the
effort will be worth it.
Thanks again for your help
--
John
Received on Sat Aug 23 2014 - 01:33:41 UTC