Torsten Foertsch wrote:
On Wed 16 Jul 2008, Geoffrey Young wrote:
I'd be interested in
recording all the values passed in and see if they match during start
and restart.
here you are.
The attached file is written with this print statement:
print $f "$$=".(syscall 39).": ".($path // "
Now, AT experts are needed to mull over:
1) why don't the error message show up in the error_log
2) is the enclosed patch a sufficient cure or does it rather hide a real
problem (why is $ENV{PATH} undef in the first place)
The strace output for that process starts with these lines:
setsid()
