At 8:02 AM +0100 3/22/02, Gerald Richter wrote: > > I have to have a >> <perl> >> </perl> >> block in the config file. >> > >Mmh, I never had a need to do this...
Do you have a startup.pl, or anything else that would cause mod_perl to run code during initialization? I suspect that's all it takes. > >> embperl_ApacheInitCleanup has to call ap_remove_module >> (&embperl_module) every time, not just when mod_perl.c is dynamic. >> > >That's what I first also had, but when you call it always it won't work on >my static compiled mod_perl's anymore. Hmm, and mine is static and needs it. Clearly another variable here. >For the static builds that I had tested, the Perl interpreter was only >initialized once, so Embperl must only initalize once, while for dynamic >builds mod_perl is unloaded after the first pass and Embperl has to make >sure it gets unloaded before (that's what embperl_ApacheInitCleanup does) One work-around I thought about was forcing mod_perl to shutdown when the config file is re-read, but that seemed a bit too much like a hack, although there's a certain logic to it. >Yesterday I talked to somebody who has exactly the same problem as you and >is not running mac osx, so maybe we find out what specifc on those Well, that makes me feel a bit better. This was getting so weird that there was always this feeling in the back of my mind that maybe I was doing something stupid. Do you know what OS they are running? -- Kee Hinckley - Somewhere.Com, LLC http://consulting.somewhere.com/ [EMAIL PROTECTED] I'm not sure which upsets me more: that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
