Hi Sven
my approach doesn't suffer of the probable bug you have just pointed
out,
because I always assume to be working from a definite directory, so I
don't
have at reach something to reproduce it.
Would you please add a few 'apache_error_log' commands to your scripts
to
track down consistently both script path and [pwd] output?
That could help explain in what either Rivet or your scripts fail.
Thanks
-- Massimo
On 18.01.2012 13:49, Sven wrote:
Hi Massimo,
I tried your approach with success. I added
RivetServerConf BeforeScript "load_env reqenv; cd [file dirname
$reqenv(SCRIPT_FILENAME)]"
to our Rivet directives.
But I'm not quite sure if this the right place for the command.
Because for me it is the correction of a misbehaviour. But as long as
it is not clear who is guilty and if there is not introduced an
unwanted side-effect, this way sounds as a good solution.
Thanks and best regards
Sven
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
