Even more OT, we might try setting up the PyPI server under supervisord (http://supervisord.org) plus superlance's HTTPOK and memmon event listeners. This would make sure that the process is restarted when it stops answering HTTP requests or if it begins to consume "too much" memory. It's slightly more reliable than other systems that do similar things, because it's the parent process of the processes being monitored.
On Wed, 2010-06-16 at 12:03 +0000, Antoine Pitrou wrote: > M.-A. Lemburg <mal <at> egenix.com> writes: > > > > Setting up some Zenoss or Nagios monitoring system to take > > care of monitoring the PyPI server (and our other servers) > > would be a separate project. > > Just for the record, I would mention that someone started a rewrite of the > Nagios software in Python: > http://www.shinken-monitoring.org/ > > According to the author, the Python rewrite is also much faster than the > original C software: > http://www.shinken-monitoring.org/features/huge-performances/ > > Probably a good showcase of the "using a dynamic language allows you to focus > on > a better architecture" argument :-) > > Regards > > Antoine. > > > _______________________________________________ > Catalog-SIG mailing list > Catalog-SIG@python.org > http://mail.python.org/mailman/listinfo/catalog-sig > _______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
