>>> On 2/2/2010 at 10:28 AM, in message <4b6860c0.9070...@pocock.com.au>, Daniel
Pocock wrote:
>> If tcpconn is functioning normally after the initial startup, then that
> basically answers the questions. It appears that at least on CentOS/RHEL5
> python is not yielding after calling start() a
> If tcpconn is functioning normally after the initial startup, then that
> basically answers the questions. It appears that at least on CentOS/RHEL5
> python is not yielding after calling start() and therefore not allowing the
> threading module to call the threads run() method. The result i
>>> On 2/2/2010 at 9:57 AM, in message <4b68598e.6050...@pocock.com.au>, Daniel
Pocock wrote:
> Brad Nicholes wrote:
> On 2/2/2010 at 6:23 AM, in message <4b682769.6000...@pocock.com.au>,
> Daniel
>
>> Pocock wrote:
>>
>>
>>> I've just been testing r2258 on CentOS 5. rpm
Brad Nicholes wrote:
On 2/2/2010 at 6:23 AM, in message <4b682769.6000...@pocock.com.au>, Daniel
> Pocock wrote:
>
>
>> I've just been testing r2258 on CentOS 5. rpmbuild runs successfully
>> and the packages install and run.
>>
>> However, I notice that some of the tcpconn
>>> On 2/2/2010 at 6:23 AM, in message <4b682769.6000...@pocock.com.au>, Daniel
Pocock wrote:
>
> I've just been testing r2258 on CentOS 5. rpmbuild runs successfully
> and the packages install and run.
>
> However, I notice that some of the tcpconn metrics are failing.
> tcpconn.py doesn't
I've just been testing r2258 on CentOS 5. rpmbuild runs successfully
and the packages install and run.
However, I notice that some of the tcpconn metrics are failing.
tcpconn.py doesn't appear to have changed since r1658 (August 2008). It
is the only python module that is loaded by default
