Hi,
We have several Solaris 10 running an application that generates large text
logfiles
We need to stream these logfiles in realtime to a central monitoring server.
Unfortunately (for both technical and non-technical reasons), we can't use
an NFS-mount. At the moment, we're using SSH with tail
On Tue, Sep 27, 2011 at 07:48:20AM +0800, Don Li wrote:
> Hi,
>
> I have facing a problem:
> "According to the Python memory pool mechanism, the memory usage will take
> up more and more in a long-running daemon process.
> "In the long sustained logon and logout logic by a lot of users , Twist
Hi,
I have facing a problem:
"According to the Python memory pool mechanism, the memory usage will take
up more and more in a long-running daemon process.
"In the long sustained logon and logout logic by a lot of users , Twisted
process MUST stop restarting because the memory usage."
With "me
On Mon, Sep 26, 2011 at 01:37:16PM +0200, Laurens Van Houtven wrote:
> The obvious solution is to have a makeClient function defined in module
> scope for the given test module. I could then have a bin/liveTest.py that
> takes a username, password and cert, and monkeypatches that module. I'm
> assu
On Sep 26, 2011, at 7:37 AM, Laurens Van Houtven wrote:
> Are there any better ways to pass test data to trial?
Environment variables.
This isn't a great option, but I'd say it's definitely a better one than
modules which monkeypatch stuff.
You can also have your test cases synthesize stuff o
On 12:13 pm, a.lib...@gmail.com wrote:
Regarding
The process ''starting'' is different from `ProcessProtocol` methods
being
called. `ProcessProtocol.processEnded` is ''not'' called until the
reactor is running.
On my own VMs, the processEnded gets called
[root@master1 play]# cat fun.py
Regarding
> The process ''starting'' is different from `ProcessProtocol` methods being
> called. `ProcessProtocol.processEnded` is ''not'' called until the
> reactor is running.
On my own VMs, the processEnded gets called
[root@master1 play]# cat fun.py
from twisted.internet import reactor
Hey,
In order to properly test txievery (a twisted library for dealing with
Paypal's APIs), I'm building a mock Paypal server. The idea is to run the
same high-level tests (which basically use the API and eventually make it
make real HTTPS requests) against both the mock server and the Paypal
San
On 23/09/11 20:33, gary jefferson wrote:
> So, am I missing some other more elegant solution? Is there really no
> way to turn async, deferred-returning twisted code into synchronous
> result-returning code, via clever use of wrappers etc?
Run the reactor in another thread, or another process and