Bhavin Turakhia wrote: > Redhat 7.1 > Apache 1.3.22 > Midgard 1.4.1-5 > > I get in my apache log > > [Sat Dec 22 06:29:35 2001] [debug] midgard.c(394): [client 203.197.8.193] > Cannot get midgard module config > [Sat Dec 22 06:29:42 2001] [notice] child pid 24956 exit signal Segmentation > fault (11) > [Sat Dec 22 06:30:05 2001] [debug] midgard.c(394): [client 203.199.75.157] > Cannot get midgard module config > [Sat Dec 22 06:30:11 2001] [debug] midgard.c(394): [client 203.197.8.193] > Cannot get midgard module config > [Sat Dec 22 06:30:21 2001] [debug] midgard.c(394): [client 203.197.8.193] > Cannot get midgard module config > [Sat Dec 22 06:30:23 2001] [notice] child pid 24957 exit signal Segmentation > fault (11) > [Sat Dec 22 06:30:25 2001] [debug] midgard.c(394): [client 203.197.8.193] > Cannot get midgard module config > [Sat Dec 22 06:30:35 2001] [notice] child pid 24980 exit signal Segmentation > fault (11) > [Sat Dec 22 06:30:37 2001] [debug] midgard.c(394): [client 203.197.8.193] > Cannot get midgard module config > [Sat Dec 22 06:30:50 2001] [notice] child pid 24958 exit signal Segmentation > fault (11) > > These errors stop coming if i COMMENT out the 'extension midgard.so' in > php.ini. > > What I wanted to know is - > > 1. how do i eliminate these errors
It's a known 1.4.1 problem with serving non-midgard requests. Please upgrade to 1.4.2 > 2. Is there any issue (performance or otherwise) in commenting the loading > of themidgard.so extension The default midgard root page will load the extension dynamically for each separate request. I would expect a noticeable performance decrease. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
