[mythtv-users] Re: mythweb2 having some more problems

[Chris Petersen]

> I think you're mistaken on mysql_pconnect. When you use mysql_connect, the
> connection is automatically closed when the script ends.

yeah, I never said that it didn't close them.  just that it did open
them.  My assumption is that with the average mythweb box, there will be
one, maybe two, simultaneous connections.  

> The situation where you really want mysql_pconnect is a dedicated webserver
> running a specific app. Since every request will be using the same type of
> database connection, it makes sense to use mysql_pconnect.

which is exactly what mythweb is doing.  well, on most machines.

> Although I don't think mythweb should use mysql_pconnect by default, it
> shouldn't be causing problems like this for average myth users. 

it's not.  SHOW PROCESSLIST is showing a bunch of mythtv connections,
and no apache connections, despite the fact that I've been reloading
pages in mythweb for the past couple of minutes.

This tells me that apache is cleaning up its child threads pretty
quickly (thus, not an "indefinite" connection).  The funny thing is that
the mythbackend-spawned connections started growing, and after sitting
relatively idle for the past 20 minutes, they haven't gone away. 
(granted, I haven't updated to today's cvs, and Isaac says he fixed some
of this stuff).

Anyway, pconnect is NOT the problem.

-Chris