It doesn't seem to have any impact on the tests (as I was able to install mod_perl.1.99_12 without a problem). It does throw an error right before the test server starts up.
The command being issued is "ulimit -c unlimited". According to my ulimit manpage, the correct command is "ulimit unlimited" (which I have tested).
Are you sure? Where does it tell to set only the core files limit. Won't it unlimit everything? please check the manpage again. e.g. tcsh syntax is:
% limit coredumpsize unlimited
but it still specifies what attribute to set.
So how do we uniquily identify your platform from perl to pick the right arguments? there should be a combination of $^O and probably $Config{osvers}. I think $^O is not enough, since others running on Solaris didn't have this problem.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
