--- "Keith Kwiatek" wrote:
I just wanted to ask if anyone had this happen to them....I was NOT blaming
apache::session! I did want to find out what I AM DOING WRONG! .....or if it
is a problem with solaris..... any happy silient users using solaris with
apache::session?
--- end of quote ---
FWIW, I've got some debugging to do on a script on Solaris 7 (Apache/1.3.9 (Unix)
mod_perl/1.21 PHP/3.0.14 mod_ssl/2.4.10 OpenSSL/0.9.3a) that uses Apache::Registry and
Apache::DBI and will occasionally go totally insane, and spike httpd at like 30% CPU
(ultrasparc2) and, what's weird (and probably a clue), is if I get three or four of
these going, the process table gets full. Neat, eh? ps and top are uncooperative
thus far. I think DBD::Sybase may be involved, but its unproven.
Here's a general question - if I run httpd -X so I can use Apache::Status to check DBI
connections, etc, and the process goes nuts, I can't use Apache::Status. How then to
debug the nutty session?
Thanks,
-Bill