On Tue, 2008-11-04 at 14:31 +0100, Matthias Urlichs wrote:
Scott James Remnant:
The idea would be that when the pre-start script exits, we pick up the
environment table and add that back to the job -- this may require some
changes to the way init gets child signals or something though.
Hi,
Scott James Remnant:
The idea would be that when the pre-start script exits, we pick up the
environment table and add that back to the job -- this may require some
changes to the way init gets child signals or something though.
Umm, so you want to either auto-add a printenv at the end of
On Thu, 2008-10-30 at 20:16 -0700, Garrett Cooper wrote:
Just doing some more testing and while I understand while this would
most likely not work, I'm still wondering if it's documented or not:
Assuming that you mean that the environment of the child scripts doesn't
affect the job, that's a
On Thu, Oct 30, 2008 at 11:26 PM, Matthias Urlichs [EMAIL PROTECTED] wrote:
Hi,
Garrett Cooper:
env VAR=0
Don't forget that environment variables are inherited from parent to
child. That's _it_.
echo POST MESS: $VAR
... so this would probably print zero, if it was actually used to stop
