comment on

As far as the mod_perl-list thread is concerned, the reader lays it out there... yes, it appears this individual may be having problems with DSO and mod_perl, but the alternative is to compile Apache without any DSO support? Come on!

Ahem. ;>

This "mod_perl DSO == bad" approach that I am coming from is not so much the result of an evening of research, but more the result of over a year lurking on the mod_perl lists. You are not the first to challenge that most of the eviednce against DSOs is anecdotal -- again, see the list.

Also just my two cents. Personally, I have seen no reason not to compile it statically, and some personal experience with segfaults caused by mod_perl as a DSO. Hence, I will continue to err on the side of caution (and also speed :) and build mod_perl in statically.

perl -pe '"I lo*`+$^X$\"$]!$/"=~m%(.*)%s;$_=$1;y^`+*^e v^#$&V"+@( NO CARRIER'

In reply to Re: Re: Re: problem in mod_perl installation by Chmrr
in thread problem in mod_perl installation by premjhere

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks