But how would he know where his .conf file is installed?
If he could find where his .conf file is installed, he could just put
the data there.
On 6/11/2012 8:19 PM, Joshua Marantz wrote:
I think we are saying the same thing, right? To "tell his module" I'm
suggesting he write the path where the .so is installed into his .conf file
so that he can get the path at runtime.
On Mon, Jun 11, 2012 at 8:02 PM, Jerry Stuckle<je...@smartechhomes.com>wrote:
In that case he should also be able to tell his module where the files are.
On 6/11/2012 7:40 PM, Joshua Marantz wrote:
I think he wants to write bytecodes during module installation when he
will
have write access.
During installation can you also write a .conf template showing your
module
where the bytecodes are?
Josh
On Jun 11, 2012 7:29 PM, "Jerry
Stuckle"<jerry@smartechhomes.**com<je...@smartechhomes.com>>
wrote:
On 6/11/2012 5:49 PM, Ben Noordhuis wrote:
On Mon, Jun 11, 2012 at 10:10 PM, Bart Wiegmans<bartwiegmans@gmail.****
com<bartwiegm...@gmail.com>>
wrote:
Hello everybody,
For a project I'm doing, I need to install a few bytecode files
alongside my module. I was planning on placing them in the modules
directory but I realised that at runtime I do not know where that is.
What is more, that directory may (and will, as a matter of fact) vary
during installation and testing. But most importantly, the server
knows where the module is kept as it specified by LoadModule.
So in short, how can I determine the directory of my module at runtime?
You can't, the file path is internal to mod_so.c. I don't think it
even stores it.
In addition, there is no guarantee you have write access to that
directory.
