I am using SuSE 8.0 with Apache 1.3.26 and the latest
PHP and Midgard. I did a source installation because
Midgard did not work at first as compiled in, but when
I removed the rpm, it took the Apache init.d script
and I couldn't find a copy that I was smart enough to
get to work with this installation. I tried starting
and stopping manually for a while, but I am working on
a laptop which is shutdown frequently for transport
and I was forever forget to cut Apache on or off.

I put the rpms back in, and surprisingly, they worked.
(My experience with rpms and modules has not been
good.) However, though some funky mechanism, I have
yet to completely figure out, SuSE has made it
possible to roll in a whole bunch of modules like
mod_perl, ssl, JServe, php, zope, midgard, xml, etc.
that are a pain to combine altogether. And they all
work, except for Midgard, which I think would work if
I could get the databases constructed. 

I am assuming ./dbinstall would do that if I could
find where to run it, but I tried running it in every
directory midgard appeared to no avail. 

I couldn't find anything on the Midgard site, but I do
read German so I'll take a look at the site you
offered. If you have any further ideas, I'd love to
hear them. LD


--- [EMAIL PROTECTED] wrote:
> Hi,
> 
> >
> >I have a rpm version of midgard from SuSE. It looks
> What Version? I tried the RPMs with SuSE up to 7.3
> You are better off if you
> compile midgard from source.
> An excellent german installation-guide can be found
> at www.olav.net
> 
> >like I need to run ./dbinstall, but it won't run
> under
> >the /usr/bin/ directory where mysql is located or
> from
> >/usr/sbin/database-upgrade or any of the other
> midgard
> >directories.
> >The reason I think ./dbinstall needs to be run is
> that
> >I get a SuSE test page when I run 127.0.0.1:8099,
> >127.0.0.1:8101 or 127.0.0.1:8102. Is that a correct
> >assumption?
> The new versions all run at port 80 (unless you want
> it otherwise)
> 
> >Also, I cannot get my Apache server to operate on
> >anything other than 127.0.0.1. I get a "Connection
> was
> >refused when attempting to contact localhost"
> error. I
> >have localhost set as Apache's server name. I'm
> >running name resolution from an /etc/hosts file
> with
> >entries for 127.0.0.1 localhost and 192.168.10.10
> >servername.domain  servername. Could this be
> causing
> >the problem listed above?
> You can configure apache to listen to both ip's...
> check /etc/httpd/httpd.conf for that.
> 
> >Thanks for any help on either of these problems.
> >Sincerely,
> >LD
> >
> Hope I could help,
> 
> med-men
> 
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to