RE: Bugs 5.6.0 modperl use?

We are running 5.6 on 2 production servers with mod_perl 1.23 and 1.24, Apache 1.3.12, Apache::DBI, DBD::Sybase (to MSSQL), and DBD::mysql. One box is Linux. The other is Solaris 2.7. So far no issues other than "depreciated" notices on some modules, and our own programming errors. Serving ~6M

Want to work at a Game company?

INTERNET DEVELOPER If you like the idea of working with unique, talented people and wearing jeans and a t-shirt to work, you're just the person we're looking for. Origin is a long-standing leader in the PC-gaming industry, and an acclaimed pioneer in the online gaming genre. We create Virtual

RE: Want to work at a Game company?

- From: Jason Bodnar [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 18, 2000 12:00 PM To: Buddy Lee Haystack Cc: [EMAIL PROTECTED]; Graf, Chris Subject:Re: Want to work at a Game company? Yes it is. Doug has always encouraged mod_perl related jobs to be posted to this list. On 18

RE: newbie question - require

Check the mod_perl guide for the usage of require() and do(). You probably want to use do() instead of require(). Chris -Original Message- From: Brett Lee [mailto:[EMAIL PROTECTED]] Sent: Monday, May 15, 2000 7:56 AM To: [EMAIL PROTECTED] Subject: newbie question - require In moving

Apache::DBI with Sybase - What's wrong?

It seems that once processes start getting reused, I wind up with a ton of DB error messages in my error_log. They seem to start like this: ct_cmd_alloc failed at /usr/local/lib/perl5/site_perl/5.005/sun4-solaris/DBD/Sybase.pm line 159. DBD::Sybase::db ping failed: OpenClient message: LAYER =

RE: Apache::DBI with Sybase - What's wrong?

Thanks Michael. If anyone can explain a little better what Apache::DBI and mod_perl are doing, or should be doing at this point, that may be helpful. I have been testing a little more and found that no errors will appear unless I am actually doing something with the connections. If I just