> > Should Midgard run now?, and if so, how do I fire it up?
>
> No, it looks like you still need the PHP3 module, which includes
> the Midgard modifications.
>
> [paul@www paul]$ /usr/sbin/httpd -l
> Compiled-in modules:
> http_core.c
> mod_so.c
> mod_ssl.c
> mod_php3.c
> mod_midgard.c
> suexec: disabled; invalid wrapper /usr/sbin/suexec
>
> ------------------------------------------------------------------------
OK - so here is httpd -l ;
# /www/bin/httpd -l
Compiled-in modules:
http_core.c
mod_env.c
mod_log_config.c
mod_mime.c
mod_negotiation.c
mod_status.c
mod_include.c
mod_autoindex.c
mod_dir.c
mod_cgi.c
mod_asis.c
mod_imap.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_access.c
mod_auth.c
mod_so.c
mod_setenvif.c
mod_php3.c
mod_midgard.c
suexec: disabled; invalid wrapper /www/bin/suexec
and HEAD / HTTP 1.0 shows;
Server: Apache/1.3.12 (Unix) Midgard/1.2.5 PHP/3.0.12+Midgard/1.2.5
but when I bring up a simple test.php3 file like
<html>
<head>
<title>Example</title>
</head>
<body>
<?php echo "Hi, I'm a PHP script!"; ?>
</body>
</html>
Is just displays the code as above in Netscape
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
