>>> On Tue, Aug 12, 2008 at 7:51 AM, in message
<[EMAIL PROTECTED]>, Kostas Georgiou
<[EMAIL PROTECTED]> wrote:
> On Mon, Aug 11, 2008 at 12:08:29PM -0600, Brad Nicholes wrote:
>
>> Actually this issue really isn't that hard solve. The python
>> capability is all implemented in the C module mod
On Mon, Aug 11, 2008 at 12:08:29PM -0600, Brad Nicholes wrote:
> Actually this issue really isn't that hard solve. The python
> capability is all implemented in the C module mod_python. When
> mod_python's init() function is called, it simply reads the python
> module directory from it's configu
>>> On 8/9/2008 at 2:22 PM, in message <[EMAIL PROTECTED]>, Carlo Marcelo
Arenas Belon <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 04, 2008 at 08:40:43PM +0100, Kostas Georgiou wrote:
>>
>> I've noticed that the python scripts are always initialized even if they
>> don't have any metrics collected.
>
On Mon, Aug 04, 2008 at 08:40:43PM +0100, Kostas Georgiou wrote:
>
> I've noticed that the python scripts are always initialized even if they
> don't have any metrics collected.
right, that is a bug as the only way to "disable" a python script currently is
to rename it so it won't be found by gmo
Hi,
I've noticed that the python scripts are always initialized even if they
don't have any metrics collected. In most cases this isn't too bad
(assuming module_init doesn't do anything too invasive) but for example
tcpconn.py starts a thread running netstat that will keep running even
if nobody c
