Re: Using different versions of perl libraries with same name

2004-10-04 Thread Ryan Underwood
:PerlVINC module to load still) and reloads are blazing fast. Any idea what goes on here? -- Ryan Underwood, <[EMAIL PROTECTED]> -- 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

Re: Using different versions of perl libraries with same name

2004-10-03 Thread Ryan Underwood
d if using modperl2, see: > http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_ > > Ryan, please always mention what modperl version you are using, so we > don't have to guess. Thank you. Sorry about that, this is mod_perl version 1. -- Ryan Underwood, <[EMAIL PROTECTED

Using different versions of perl libraries with same name

2004-10-02 Thread Ryan Underwood
ySite/MySite_Site1/g, and eval the resulting string. But I'm not enough of a Perl guru to know whether that will work or not. So I'm here soliciting advice. I hope that was somewhat clear and that I'm not crazy thanks, -- Ryan Underwood, <[EMAIL PROTECTED]> -- Rep

Re: mod_perl sometimes prints to error log instead of client

2004-09-24 Thread Ryan Underwood
On Fri, Sep 24, 2004 at 02:45:14PM -0400, Perrin Harkins wrote: > On Wed, 2004-09-22 at 23:58, Ryan Underwood wrote: > > I might have figured it out. The program wasn't closing STDOUT at the > > end of printing stuff to the client. Is this a known boo-boo? > > I don&

Re: mod_perl sometimes prints to error log instead of client

2004-09-22 Thread Ryan Underwood
I might have figured it out. The program wasn't closing STDOUT at the end of printing stuff to the client. Is this a known boo-boo? Anyway, I haven't seen the problem yet after restarting apache, so I'm crossing my fingers now. -- Ryan Underwood, <[EMAIL PROTECTED]>

Re: mod_perl sometimes prints to error log instead of client

2004-09-22 Thread Ryan Underwood
). The client's connection is dropped before Apache even gets into the mod_perl code. The weirdest thing about this is that even though it seems to have nothing to do with my code now, it _only_ happens on the mod_perl vhost. Not on any other vhosts, even ones running the same program in C

Re: mod_perl sometimes prints to error log instead of client

2004-09-22 Thread Ryan Underwood
e page repeatedly. Sometimes it completely works 10/10 times. Other times it works 5/10 times or 0/10 times. It seems completely random but if I could just figure out what's happening to STDOUT it might shed some light on the trouble. -- Ryan Underwood, <[EMAIL PROTECTED]> -- Repo

Re: mod_perl sometimes prints to error log instead of client

2004-09-21 Thread Ryan Underwood
On Wed, Sep 08, 2004 at 02:19:17PM -0400, Perrin Harkins wrote: > On Mon, 2004-09-06 at 23:15, Ryan Underwood wrote: > > I've had this strange problem off and on ever since we started using > > mod_perl. Occasionally, when the page is generated and printed, the > >

Re: mod_perl sometimes prints to error log instead of client

2004-09-08 Thread Ryan Underwood
x27;t get Dynagzip to work correctly with a nph CGI script either. There is an option UseCGIHeadersFromScript but it appears to have no effect in the code. So I scrapped its usage for the time being. -- Ryan Underwood, <[EMAIL PROTECTED]> -- Report problems: http://perl.apache.org/bugs

Re: mod_perl sometimes prints to error log instead of client

2004-09-08 Thread Ryan Underwood
On Wed, Sep 08, 2004 at 02:19:17PM -0400, Perrin Harkins wrote: > On Mon, 2004-09-06 at 23:15, Ryan Underwood wrote: > > I've had this strange problem off and on ever since we started using > > mod_perl. Occasionally, when the page is generated and printed, the > >

mod_perl sometimes prints to error log instead of client

2004-09-06 Thread Ryan Underwood
ode=print PerlHeaderParserHandler "sub { tie *STDOUT, 'Apache' unless tied *STDOUT; }" # Normal stuff Options ExecCGI allow from all # Emulate nph-*.cgi PerlSendHeader off # Give us %ENV