Subject: Re: memory tester shows up swap/page tuning bug [was Re: BUFFERCACHE, PR 1903]
To: None <Chris_G_Demetriou@ux2.sp.cs.cmu.edu, jonathan@dsg.stanford.edu>
From: Grey Wolf <greywolf@siva.captech.com>
List: current-users
Date: 09/16/1996 11:20:12
So make it mode 500 owned by root.  What's the problem?

Besides that, what's to keep someone from writing their own?

# From Chris_G_Demetriou@ux2.sp.cs.cmu.edu Sun Sep 15 09:51:36 1996
# Delivered-To: current-users-outgoing@NetBSD.ORG
# To: Jonathan Stone <jonathan@dsg.stanford.edu>
# cc: current-users@netbsd.org, laine@morningstar.com
# Subject: Re: memory tester shows up swap/page tuning bug [was Re: BUFFERCACHE, PR 1903] 
# Date: Sun, 15 Sep 1996 12:47:55 -0400
# From: Chris G Demetriou <Chris_G_Demetriou@ux2.sp.cs.cmu.edu>
# Delivered-To: current-users@NetBSD.ORG
# 
# > That should be /usr/sbin/chill ;).  If we care about VM performance
# > under overload conditions, shipping some kind of memory hog isn't such
# > a bad idea.
# 
# Yes it is.  In fact, it's bloody stupid.
# 
# Why give random users using somebody else's box a ready-made
# performance killer?  Even _if_ "vm performance under overload
# conditions" were "OK," it'd be much worse than if _not_ under overload
# conditions.
# 
# Basically, you add a new binary whose only purpose is to eat memory,
# and you've created yet another annoyance for anyone concerned with
# what users do on his or her machine.
# 
# 
# chris
# 

				--*greywolf;