[Phpwiki-talk] Apache2 problems (was Need help with Wiki)

[Reini U. <ru...@x-...>]

Reini Urban schrieb:
> Joel Sherrill <jo...@OA...> schrieb:
>> ReymanX wrote:
>>
>>>> First, we do not seem to be able to get any password
>>>> setup to work.  If someone sets it in their preferences,
>>>> and doesn't edit their personal page, they get locked out.
>>>
>>>
>>> I have the same problem before, then I upgrade to phpwiki-1.3.11pre
>>> from CVS. I use to use suse 9.1 with apache 2.0, but it's not working.
>>>  Then I use debian with apache 1.3.x, it's work now.
>>
>>
>> As I mentioned in another email, we are using Fedora Core 1
>> which includes Apache 2.0.  This is not the only thing hosted
>> on this machine so switching versions or distributions is
>> not something we would undertake lightly.
>>
>> I just reported that we are having all sorts of weird problems
>> with preferences. :(
> 
> 
> yes,
> we know that > 1.3.8 doesn't work whth fedora core yet.
> strange apache2 issue.
> 
> I got it working somehow previously but It was a major hack described 
> somewhere.
> or use an older release.
> 
> I'll look into these apache2 issues soon. first let me finish my 
> testsuite for the more important errors.

Well, this problem raised its importance from low-scale to highest, 
since this is the new configuration we'll have to deal with at the news 
sf.net web servers.
The new sf.net will have fedora (oh my god! from debian to fedora), 
Apache 2 and php-4.3.8.
Still with the pcre problems, but 4.3.8 has more effective memory 
handling than 4.1.x. It needs 2MB less.

> BTW: I had to switch http://phpwiki.sf.net/phpwiki back to the old mysql 
> version. with gdbm and this php I got no sessions working. and the db is 
> sometimes in a stale lock state.

The gdbm locking problems seems to be serious, since gdbm is vastly 
preferred over anything else.
(See http://phpwiki.org/PhpMemoryExhausted/Testresults)
At least php-4.3.x with gdbm will now support file-level locking, so our 
own software locks are not be that critical anymore. (stale locks after 
errors)

Those session problems are typical if USECACHE is off. Then ob buffering 
is ineffective, and the session cookies are not handled properly, since 
some part already printed some character.
-- 
Reini Urban
http://phpwiki.org/