[21896] in Hotline Meeting

home help back first fref pref prev next nref lref last post

software and configuration changes

daemon@ATHENA.MIT.EDU (Kimberly Carney)
Fri Mar 25 14:26:32 1994

To: op@MIT.EDU
Cc: hotline@MIT.EDU
Date: Fri, 25 Mar 94 14:26:15 EST
From: Kimberly Carney <kim@MIT.EDU>


We're approaching the end of the spring semester, which is typically
the time of year when Athena services are at highest usage. Over the next 
several weeks we need to strive to make sure the environment remains
as stable as possible.

I think one of the most important things we can do to ensure stable
and reliable service is to freeze the configuration of the production
servers. So, between now and the end of the semester only in cases of 
emergency should software configuration changes be made to the production 
environment. This includes afs file servers, afs database servers, license 
servers, zephyr, hesiod, print servers, boot servers, etc. If you have
any questions about what constitutes "an emergency" just ask me or Jeff.

Several other things are important in operating our environment.
First, prevention of problems. Pay special attention to the daily reports. 
Second, early detection of problems. I think the noc helps out a lot 
here. (Let's check the noc paging to make sure the paging info is up to 
date.) Third, quick response and resolution to the problems that do 
inevitably occur.




home help back first fref pref prev next nref lref last post