🚀 go-pugleaf

|> 
|> 
|> I have a DECstation 5000/240 targetted as an applications and file server
|> for roughly 30-40 DECstation 5000/25 Maxines.  No one client is going to
|> be any major load.  No user files or critical OS files are going to be
|> on the server, just some applications that are best served (FrameMaker),
|> and a few work-related files.  I intend to run the server as a mail and
|> Hesiod "hub", and it may be called upon to serve a half-dozen MS-DOS
|> clients via NFS as well as what's listed above.  The server has 32 MB
|> of RAM, plenty of disk, and will be headless, to the best of my knowledge.
|> 
|> My question is:  What sort of configuration changes will I need to
|> be doing to optimize the performance and effectiveness of the 240
|> as a server?  What sort of software should I be running?  Help!
|> 
|> 
|>                                              ...Sensei
|> 
|> ==
|>  Internet:  sensei@dojo.mi.org
|>  UUCP:  ...!wsu-cs!dojo!sensei                      
|> 
I am running a DECstation 5000/200 as a server and all we did was to set the 
buffcache to about 50% to set aside a bunch more memory for file caching.
We run dataless configuration with /usr being exported to the clients and 
/ root and swap on each workstaton.  The one thing I would suggest to really
speed up writes is to add a prestoserve board.  I have one on my 5900 and 
it really makes it zip.  I can actually feel the difference when I turn it off.

Probably the most important thing is to disable logins to the server.  I
made the 
mistake of letting one person compile on the server and all hell broke
loose.
Next thing I knew is that we were getting nfs timeouts and everyone
started 
logging into the server to work (because of all the timeouts).  Don't
let that
happen to you.

Cheers, Keith
kchiles@arac.llnl.gov