>> Sorry...the "page cannot be displayed" error (from browser page) is
actually
>> a "cannot find server" (displayed on head title). i don't think this
makes a
>> difference, but just in case it does, you know it.
>Might be significant, but it could be you're using IE. IE is vague (oh
>sorry, 'user friendly') in it's error messages.
yes, using IE.
> If i comment out midgard from httpd.conf (and keep php4), leave midgard.so
> in php.ini, apache starts, but php files give page cannot be displayed
> error. (no seg fault)
>Aditya, could you try going back to to CVS as of
>July 8th? The last major change introduced were the destructors on the
>9th.
Sure..
> If i leave midgard uncommented in httpd.conf, then seg fault.
>> >- no mod_midgard, midgard-php enabled: server segfaults at startup. The
>> >patch does not log anything to stdout or the error log.
>> NO...if mod_midgard is disabled(httpd.conf), midgard-php(php.ini) is
>> enabled, then get page cannot be displayed error for php files. nothing
in
>> error_log
>And nothing on stdout? But pages do not parse, and apache keeps
>running?
php pages don't get parsed..(cannot find server/page cannot be displayed)
well...this is interesting...in netscape 4.7 i get this:
"The document contained no data. Try again later, or contact the server's
administrator"
> >- mod_midgard enabled, no midgard-php: server segfaults at startup, no
> >text to stdout or error log.
> Yes...but...stdout?? that's just the ouptut from httpd -X? if yes, then
> yes, you are correct...no text to stdout (other than Segmentation fault
> (core dumped) )
>Yes, stdout is text to the screen. So mod_midgard dies instantly,
>leaving no trace in the log. OK, I'll look for potential troublespots,
>and create a logging patch.
ok.
Aditya
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
