[Zope] memory-leak, would the chrism-setrlimit "patch" help?

[Chris McDonough]

The rlimit stuff never made it to a released Zope.  It's too big of a
hammer for the problem... instead of gracefully restarting, it begins to
throw MemoryErrors when the resource limitation is exceeded.  AutoLance
is a better way to do this.  AFAIR, AutoLance worked under 2.7.  What's
not working?

On Tue, 2004-09-07 at 10:31, Sascha Ottolski wrote:
> Hi,
> 
> I'm just wondering if anyone knows why this way of restarting zope in 
> case of memory leaks never made it to the HEAD?
> 
> http://cvs.zope.org/Zope/Attic/z2.py.diff?r1=1.56&r2=1.55.10.1&only_with_tag=chrism-setrlimit-branch
> 
> AutoLance used to work nice, but seems not to be updatead any more, so 
> it's no option for Zope-2.7 and linux-2.6.
> 
> I've seen some suggestions for external tests, like 
> http://www.zopewiki.org/CheckZopeMem, but chris' way seems to be so 
> much simpler. Does anyone know if the setrlimit solution has problems?
> 
> 
> Thanks,
> 
> Sascha
> 
> _______________________________________________
> Zope maillist  -  Zope at zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists - 
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )
>