interpreter crashes

Martin von Loewis loewis at informatik.hu-berlin.de
Sun Oct 28 04:58:09 EST 2001


Paul Rubin <phr-n2001d at nightsong.com> writes:

> Anyone got any suggestions?  Want to see the core dumps?  How
> frequently does this type of thing happen?  If Python is in the habit
> of crashing randomly, that may make it inadvisable to write
> long-running servers that need to stay up.  Perhaps it's more
> appropriate to write servers Apache-style, forking new processes and
> reinitializing every so often.

If you want to guarantee the service even in case of crashes (which
may not necessarily be core dumps, but could also be uncaught
exceptions), I'd recommend to put a super-simple watch daemon along
with service; if the service stops, the daemon should restart it. In
the service itself, assume it will run forever (until told to shut
down from the outside). 

Also put another computer next to the first one, to detect when the
entire computer crashes. Actually, don't put it next to it, but put it
in a different country, to deal with power outages and loss of network
connectivity :-)

Regards,
Martin



More information about the Python-list mailing list