Re: RAM usage limits

• Date: Sat, 20 Apr 1996 14:03:58 PDT
• From:
  Bartmoss <bartmoss@mistral.co.uk>
• cc: moo-cows@parc.xerox.com
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <Pine.A32.3.91.960420123631.16568A-100000@erc.jscc.cc.tn.us>

On Sat, 20 Apr 1996, Justin C Harris wrote:

> 
> 	Would it be possible to have another small task running in the
> background that keeps up with the MOO's total usage, then if the MOO's
> usage grows by 10-15 megs (or by a set number on $server_options) in a 
> very short time, it could take the necessary action to find the specific 
> process and kill it? 
> 
> 
> 
> 					Justin Harris
> 
> 
That would be a wee bit laggy, as Pavel has made it very clear that he 
will not be doing anything about this as it is not a server bug. 
The best solution is that if a site develops this problem is to monitor 
evals with out informing people. True people could use self deleting 
verbs, but in sever cases security could be tightened (might be difficult 
in a site as big as Lambda but hey). 

Chris.

• Re: RAM usage limits
• From: Justin C Harris <jch1134@jackson.freenet.org>

• RAM usage limits
• From: Justin C Harris <jch1134@jackson.freenet.org>

• Prev: RAM usage limits
• Next: Re: RAM usage limits
• Index: MOO-cows
• Thread: MOO-cows