Re: how come httpd doesn't start even though startup.pl is fine? (fwd)
On Fri, 14 Jan 2000, Ricardo Kleemann wrote: > Hmmm :-( > > On 14 Jan 2000, Frank D. Cringle wrote: > > > > > Without having checked your list, I'll wager that the "good" modules > > are all pure perl and the "bad" ones use machine-language XS > > extensions. > > So typical modules like MD5 and MIME::Body are "bad" modules? DBI, XML::Parser, mod_perl... :) -- Details: FastNet Software Ltd - XML, Perl, Databases. Tagline: High Performance Web Solutions Web Sites: http://come.to/fastnet http://sergeant.org Available for Consultancy, Contracts and Training.
Re: how come httpd doesn't start even though startup.pl is fine?(fwd)
Cliff Rayman wrote:
> i don't think he is saying that the module is "bad",
> he is saying that modules that use XS, with apache
> mod_perl have caused problems with startup and restarts.
> based on the running posts regarding
> dlopen and dlclose, i'd say he was correct.
>
> cliff rayman
> genwax.com
>
> Ricardo Kleemann wrote:
>
> > Hmmm :-(
> >
> > On 14 Jan 2000, Frank D. Cringle wrote:
> >
> > >
> > > Without having checked your list, I'll wager that the "good" modules
> > > are all pure perl and the "bad" ones use machine-language XS
> > > extensions.
> >
> > So typical modules like MD5 and MIME::Body are "bad" modules?
> >
> > Ricardo
ok, as far as i can tell apxs is not compiled right with redhat 6.1 , i
recomp'd apache 1.3.9 {dso style}and modperl1.21
and not a prob for a day now
Re: how come httpd doesn't start even though startup.pl is fine?(fwd)
i don't think he is saying that the module is "bad", he is saying that modules that use XS, with apache mod_perl have caused problems with startup and restarts. based on the running posts regarding dlopen and dlclose, i'd say he was correct. cliff rayman genwax.com Ricardo Kleemann wrote: > Hmmm :-( > > On 14 Jan 2000, Frank D. Cringle wrote: > > > > > Without having checked your list, I'll wager that the "good" modules > > are all pure perl and the "bad" ones use machine-language XS > > extensions. > > So typical modules like MD5 and MIME::Body are "bad" modules? > > Ricardo
Re: how come httpd doesn't start even though startup.pl is fine?(fwd)
Hmmm :-( On 14 Jan 2000, Frank D. Cringle wrote: > > Without having checked your list, I'll wager that the "good" modules > are all pure perl and the "bad" ones use machine-language XS > extensions. So typical modules like MD5 and MIME::Body are "bad" modules? Ricardo
Re: how come httpd doesn't start even though startup.pl is fine? (fwd)
Ricardo Kleemann <[EMAIL PROTECTED]> writes: > Hmmm :-( > > On 14 Jan 2000, Frank D. Cringle wrote: > > > > > Without having checked your list, I'll wager that the "good" modules > > are all pure perl and the "bad" ones use machine-language XS > > extensions. > > So typical modules like MD5 and MIME::Body are "bad" modules? There is nothing wrong with the modules, that's why I put "bad" in inverted commas. They are only "bad" in the sense that they trigger a bug in dynamically-linked mod_perl. -- Frank Cringle, [EMAIL PROTECTED] voice: (+49 2304) 467101; fax: 943357
Re: how come httpd doesn't start even though startup.pl is fine? (fwd)
Ricardo Kleemann <[EMAIL PROTECTED]> writes: > Hi everyone, > > I don't know what's causing this, and there are no errors being logged in > my error_log. > > I'm running apache 1.3.9, mod_perl 1.21, linux 6.1 > > I have a startup.pl with a bunch of modules in it. If I run the startup.pl > by itself it is fine, does not report errors... however, if I run httpd it > dies, never gets off the ground. try runninng 'httpd -X' under gdb. > If I go thru my list of modules and > remove some of them, then everything starts up fine... Without having checked your list, I'll wager that the "good" modules are all pure perl and the "bad" ones use machine-language XS extensions. You will need to link mod_perl statically to apache or wait for a resolution to this problem -- see the thread "Apache 1.3.9 + mod_perl 1.21 + Solaris 2.7 dumps core". -- Frank Cringle, [EMAIL PROTECTED] voice: (+49 2304) 467101; fax: 943357
