[imp] PHP Accelerator

[Sean D.]

>>>> Hi Sean!
>>>>
>>>> The workaround is to make an addition to the start/stop srcipt of
>>>> apache2 which deletes the content of the mmcache disk cache every time
>>>> a start or restart is triggered. That's all, and the problem is gone
>>>> then.
>>>>
>>>> Daniel
>>
>>
>> sweet.. now i know exactly where the issue lies...
>>
>>> Yes, but only if you are sure that it is only started/stopped via that
>>> script.  If you start/stop/restart it some other way, then it won't fix
>>> the problem...
>>>
>>> Doing this isn't a big deal, as long as everyone knows how to
>>> start/stop/restart it the required way (instead of running apachectl, 
>>> etc).
>>>
>>> -- Eric Rostetter
>>
>>
>> indeed... i use the Plesk Control Panel so i'd have to do a little
>> experimentation to find out what command plesk issues to restart 
>> apache after
>> users make config changes.  probably it issues a "service httpd 
>> restart" but it
>> might be /etc/init.d/httpd restart as they do now support SuSe and 
>> some other
>> distros besides RH.
>>
>> thanks for the good feedback guys! ;-)
>>
>> Sean
>> -- 
Daniel Eckl wrote:
 >
 > Oh, I forgot to tell that an apache _reload_ must have a cache clear,
 > too.
 >
 > Daniel
 >

hmm... perhaps i should just use different software.  phpaccelerator.co.uk was 
the one someone else reccomended but that one hasnt released a new version since 
like early 2003 i think, so i question how "active" that project is either.

Someone mentioned though using mmcache with only a ram cache and not a disk 
cache... i dont see what that would hurt. i could up mmcache's mem. allocation 
to 64 and turn off the disk cache... any how-tos on that?

Sean