I'm having trouble with zombies. Red Hat 7.1 on a Dell server with 1
GB memory. The following ps output shows a somewhat typical output.
Sometimes there are no zombies, but most of the time there are
several, and often as many as this. Performance often seems
sluggish, and I am assuming
So I'm trying to show that mod_perl doesn't suck, and that it is, in
fact, a reasonable choice.
I think one of the selling points for mod_perl is its extensibility:
modules can be written in C. Depending on the C code you have access
to, a good solution might be to try to wrap it into
Depending on how you log into the system, the
user will connect to different databases. When they do this, I store the
Database Handle from DBI/DBD as $main::dbh. This variable has the scope of
the length of processing the request and then should become undef. Easy
under normal CGI, because you
I am using mod-perl, and I am in the development stages of coding. Each time
I make a code change to a module, I must restart apache. I know there must
be docs for this, but I cannot find them from the apache web site. Could
someone assist me in finding those? Or if someone knows of a simple way
When apache is serving a ssl connection, I assume that everything
sent back and forth between the server and the client is encrypted.
I want an mod_perl script to encrypt/decrypt credit card numbers
obtained over the ssl connection for storage in a db on the server.
Is there any access to the
I don't know if there is a downside (perhaps I can't use status?),
but when I commented out the 'Apache::Status-menu_item( ...'
section, it seemed to work ok.
Tim
On Tue, 15 May 2001, James Croft wrote:
Hi,
I've just joined the list looking for an answer to this. A couple of
others
I have been trying to reduce/tune the memory requirements of an
online game which uses mod_perl (Apache::Registry). I have read the
suggestions at http://perl.apache.org/tuning/ and am trying to follow
them. The first suggestion is to preload the modules by including
Perlrequire
I have been using DBI without Apache::DBI and have been simply
storing db connections in a global variable as a sort of poor man's
persistent connection when running under Apache::Registry.
Now I want to do things "right" and am trying to understand
Apache::DBI. Before looking at the module
I am guessing that the "headless" version is what I do this when I am
doing a shockwave piece which calls cgi scripts. I create an html
version which provides a browser interface, albeit more boring, to
the same basic code so that I can more easily test the cgi side.
My strategy is to create
