Magnus Lycka wrote:
> You *could* use twisted.runner for process control even if you
> don't use twisted for your networking code. It does seem like
> a funny thing to do, but there's nothing stopping you from doing
> that. The example code in twisted.runner starts up a few shell
> scripts that die
Daniel Crespo wrote:
> Respect Twisted... Mmm... I already started with another networking
> library (TCPServer and SimpleXMLRPCServer), and I wouldn't like to mix
> things because I don't know so much about those libraries. I know that
> Twisted can do what I already have. But replacing it can be
Many thanks for your answers.
Respect Init, I need a cross platform solution. Most of times my system
will run in Win98 and XP (more on XP than 98)
Respect Twisted... Mmm... I already started with another networking
library (TCPServer and SimpleXMLRPCServer), and I wouldn't like to mix
things bec
dcrespo wrote:
> Hi to all,
>
> I'd like to have an app monitor that gets rid of another app, in the
> way that if it closes unspectedly, the app monitor just wake it up one
> more time, and viceversa.
Twisted contains such a thing. I think it's called twisted.runner,
and no, it's not just for ke
"dcrespo" <[EMAIL PROTECTED]> writes:
>> Personally, I use init as an app monitor. It doesn't need monitoring
> What's "init"? Sorry about my ignorance.
init is the first Unix process, and all other processes are descended
from it. It is the alpha and the omega of Unix processes. Uh, wait a
second
> Personally, I use init
> as an app monitor. It doesn't need monitoring
What's "init"? Sorry about my ignorance.
--
http://mail.python.org/mailman/listinfo/python-list
"dcrespo" <[EMAIL PROTECTED]> writes:
> Main application starts
> This one starts the App Monitor of itself. (This means that if Main
> Application closes, the App Monitor restart it)
>
> And viceversa means that if App Monitor closes, the Main application
> restart it.
>
> How can I accomplish thi
