Re: Perl warn failures

2003-12-17 Thread Stas Bekman
[Kit, next time you start a new thread, make sure you don't reply to one of the existing posts, but start a new one afresh. By replying to an existing post you insert a totally unrelated thread into an existing one, which confuses mail clients and some archive software. Thank you.] Kit DeKat wr

Re: Perl warn failures

2003-12-17 Thread Ged Haywood
Hello again, On Wed, 17 Dec 2003, Kit DeKat wrote: > >Are you using mod_perl? > > yes i am, i have perl environments defined in the conf file and various other > factors that are identical between all servers as well. Please read http://perl.apache.org/maillist/email-etiquette.html and please

Re: Perl warn failures

2003-12-17 Thread Ged Haywood
Hi there, On Wed, 17 Dec 2003, Kit DeKat wrote: > The old app-server was R7.3/P5.6.1/A1.3.23 (Redhat/Perl/Apache versions) > and through CVS migrated to a the new app-server, which is > R9.0/P5.8.0/A2.0.48 and afterwards our scripts starting > freezing/timeouts/partial data retrieval. H.

Perl warn failures

2003-12-17 Thread Kit DeKat
Summary: Perl pages 'lock up' silently on R9.0/P5.8.0/A2.0.48 with NameVirtualHosts and unique error_log's for each project name. The 'lock up' appears at warn statements, but only after many calls to warn. If the scripts or loops are small, they work and warn message are seen, but if there are