Path: utzoo!censor!geac!jtsv16!uunet!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!PSUVM.BITNET!W0L
From: W0L@PSUVM.BITNET ("Bill Lasher  898-6391", 814)
Newsgroups: comp.sys.sgi
Subject: Re: was Re: fsck now reboot
Message-ID: <8911130921.aa01420@SMOKE.BRL.MIL>
Date: 13 Nov 89 14:22:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29

I guess I originally got the idea at my last place of employment; they had an
IBM mainframe which they IPL'd every night, just to keep things clean.

As far as why I think we need to do it, there are a couple of reasons:

1. We do have occasional problems that rebooting seems to fix.  Things would
start to go wrong after 4 or 5 days if we didn't reboot; doing it nightly seems
to have fixed those problems.

2. I think we have problems in the first place because of the environment.  We
are running a student lab, which runs 7 days/week.  Student files are spread
out all over the net, so our S.E. from SGI wrote a routine which will mount the
user's files when they log on.  Unfortunately, we can't unmount them
automatically when they log off, so the user has to issue a command which does
the unmount for them; then they can log off.  Obviously, people forget, so
we end up with several files mounted on each machine at the end of the day.
Rebooting is the easiest way to clean up.

Also, students have a tendency to do things that make programs crash more
frequently than you might expect.  Temporary files and other wierd things get
left floating around, and rebooting cleans that up.  Since students don't have
root priveliges, automatic rebooting seems the prudent thing to do.

I'm not sure nightly reboots are really necessary, but I can't see the harm in
doing it.  I would be interested in your comments.

Sincerely,

Bill