David Banning wrote:
> > > [Wed Sep 13 16:01:52 2000] [notice] child pid 18085 exit signal
> > > Segmentation fault (11)
> > >
> > > last error again every 2 seconds
> >
> > Oh goodie. Anyway, mod_midgard is the culprit then.
> Would that be mod_midgard.c or mod_midgard.so - in either case
> how would I go about dealing with that?
mod_midgard.so is the filename of the module. The AddModule names the
source file for the module. It's an apache thing.
There's no dealing with it right now. I'll install FreeBSD 4.0 over
the weekend and will try to recreate the problem. Any existing FreeBSD
users, this is the time to pitch in with either success- or
horrorstories.
> > DocumentRoot, definately. The midgard-root.php3 file does not need to
> > be there. I usually advice against having the rootfile under the
> > DocumentRoot.
>
> Pardon me. It's my DocumentRoot which is /usr/local/share/doc/apache
> My ServerRoot has always been /www
> So should I move the root file to /www
Ah, right, this makes sense. Yes. If you don't specify a full path for
a file-related setting, it usually defaults to prepending the
serverroot to construct the full path. MidgardRootfile does this.
Anyhow, having the rootfile in the wrong location should only yield
'no data' or '404 not found' errors (I forget which), not a segfault.
> No. I have not been requesting the root file itself. I just thought
> it had to be in that spot to be executed indirectly.
OK. No, it doesn't need to be there. The DocumentRoot only applies to
the default, file-based webserving. Midgard uses that file internally,
so it doesn't need to be in the DocumentRoot.
Emile
--
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]
