Date: Mon, 10 Nov 2008 22:35:44 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org, Albert.Shih@obspm.fr Cc: Jerry McAllister <jerrymc@msu.edu> Subject: Re: PATH problem Message-ID: <200811102235.46971.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <20081110203643.GH27646@obspm.fr> References: <20081110110805.GK1302@obspm.fr> <20081110161002.GA81960@gizmo.acns.msu.edu> <20081110203643.GH27646@obspm.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 10 November 2008 21:36:43 Albert Shih wrote:
> But when I use the application throught the web it's not working. But I
> don't known how to tell apache ? mod_perl ? the PATH.
Apache.
Check the shell script /usr/local/sbin/envvars. In short, any file
in /usr/local/etc/apache22/envvars.d is sourced into the start up environment
of apache, through /usr/local/etc/rc.d/apache22 start up script. Unless a
module or script explicitly cleans the environment before forking an external
program, the variabels set at start up are preserved.
The following should work for you:
echo "export PATH=$PATH" > /usr/local/etc/apache22/envvars.d/PATH
You may want to clean out the path a bit more, pending your security policies.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811102235.46971.fbsd.questions>