On Tue, 9 Apr 2002, Stas Bekman wrote:
> Looks like you cannot run the Inline code under mod_perl. I remember
> Brian told me the secret code to make it work under mod_perl :)
Ah, this might be it. The first time the Inline code is run the ILSM
(Inline Support Module) compiles[1] the code. It then stashes this away
in the .Inline directory, then reads this 'compiled' code back in again
this, and every other time, it's called. If it can't do that then
this could be a problem.
I'd be tempted to run the code as someone who has rights to write in the
directory for the first time after I'd installed it/made any changes.
Make sure your webserver has permissions to read these files. Don't
change the source file (any part of it, even the perl part) without
rerunning the code as that privileged user (to recompile it.)
> [ snip lots of code ]
>
> make sure that /tmp/Inline is writable by the webserver.
> Hopefully you will figure out how to fix completely Bad::Segv and I'll
> have more time to do other things :) Thanks.
Um...if you do this arn't you essentially creating a directory where you
can store executable code that will be read in by your webserver and run
that can be written to by your webserver? Isn't this a little insecure?
Later.
Mark.
[1] Compiles in the looses sense of the word. Very accurate for C, less
true for other languages.
--
s'' Mark Fowler London.pm Bath.pm
http://www.twoshortplanks.com/ [EMAIL PROTECTED]
';use Term'Cap;$t=Tgetent Term'Cap{};print$t->Tputs(cl);for$w(split/ +/
){for(0..30){$|=print$t->Tgoto(cm,$_,$y)." $w";select$k,$k,$k,.03}$y+=2}
