Date: Wed, 16 Apr 1997 15:04:12 -0700 (PDT)
From: "A. Stachyra" <stachyra@u.washington.edu>
To: Hans-Gerd Berns <berns@phys.washington.edu>
Subject: Re: documentation flaws revealed

> Suggestion:  How difficult is it to write a script file for sukant to 
> cover all these steps (killing novad processes, re-initializing the 
> bit3, and whatever) with one single command line - or even with a 
> mouse click on a window on sukant?

Not very difficult.  In fact we already have something like this.  There 
are 3 shellscripts in /home/online/shellscripts called antiallclr, 
antirclear, and antirinit.  They each clean up the OD DAQ environment to 
various levels of "clean".  Of the 3, antirclear is the most powerful.
But you don't really need to know any of this.  The normal user is not 
supposed to even log into sukant and muck around.  For real convenience,
Fukuda-san has provided a shellscript available on sukonh called cleanup,
which runs antirclear (or rclear, on the ID workstations) automatically 
for you.  Thus you don't even need to log into the affected workstation 
to clean it up.  To totally clean up and reinitialize the OD DAQ, all you
need to do is totally exit run control, run the cleanup script on sukonh,
and restart run control.  When all else has failed, this solution has 
*always* worked for me.  The only challenge is to make sure that people 
know to run the cleanup script before they decide that they are out of
options.  I think we have a documentation problem, not so much a technical 
one.

A.S.