- Updated docs

SKIPPED:
	psi/utils/SerPortServer.c

doc/user/sicsinvoc.htm

@@ -29,7 +29,7 @@ Currently the following SICS clients are available:
 <li> A command line control client for sending commands to the SICS
 server and displaying its repsonses.
 <li> A status display for the powder diffractometers DMC and HRPT.
-<li> A status display for TOPSI.
+<li> A status display for MORPHEUS and general scans.
 <li> A status display for SANS and SANS2.
 <li> A status display for FOCUS.
 <li> A AMOR control and status program.
@@ -53,7 +53,7 @@ privileged SICS user.
 </p>
 <h2>Starting SICS client applications </h2> 
 <p>
-These programs can be started on a DigitalUnix system by issuing the
+These programs can be started on a Linux system by issuing the
 following commands at the command prompt:
 <dl>
 <DT>sics &
@@ -61,7 +61,7 @@ following commands at the command prompt:
 <DT>powderstatus &
 <DD> for the DMC status display client.
 <DT>topsistatus &
-<DD>for the TOPSI status display.
+<DD>for the MORPHEUS status display.
 <DT>sansstatus &
 <DD> for the SANS status display.
 <DT>focustatus
@@ -72,13 +72,9 @@ following commands at the command prompt:
 <DD> for the triple axis status display and control application.
 <DT>varwatch &
 <DD> for the variable watcher.
-<dt>trics-&
+<dt>trics &
 <dd>for the starting the TRICS graphical client.
 </dl>
-On a PC you may find icons for starting the different programs on the
-desktop.
-Each of these clients has usage instructions online which can be displayed
-through the help/about menu entry. 
 </p>
 <p>
 Another option to start SICS clients is the Java Webstart mechanism
@@ -102,41 +98,82 @@ active. A connection is established through the connect menu of the client.
 SICS is a multi user instrument control system. In order to  prevent
 malicious manipulations of the instrument SICS supports a hierarchy of user
 rights. In order to run an experiment you need at least user level privilege.
-In order to achieve this privilege you have to invoke the User Parameter/Set
-Rights dialog. There you have to enter the apropriate username and password
+In order to achieve this privilege you have to invoke the Authorize
+dialog. There you have to enter the apropriate username and password
 kindly provided by your instrument scientist.
 </p>
 <h2>Restarting the Server</h2>
 <p>
 The SICS server should be running all the time. It is only down if something
 went wrong. You can check for the presence of the SICS  server by loging in
-to the instrument computer and typing <b>CheckSICS</b> at the command
+to the instrument computer and typing <b>monit status</b> at the command
 prompt. The output will tell you what is happening. If you need to restart
 the SICS server log in as the instrument user at the instrument computer and
 invoke the appropriate command to start the server. These are:
 <dl>
 <DT>DMC
-<DD>Computer = lnsa05, User = DMC
+<DD>Computer = dmc, User = dmc
 <DT>TOPSI
-<DD>Computer = topsi, User = TOPSI
+<DD>Computer = morpheus, User = morpheus
 <DT>SANS
-<DD>Computer = sans, User = SANS
+<DD>Computer = sans, User = sans
+<DT>SANSLI
+<DD>Computer = sans2, User = sans2
 <DT>TRICS
-<DD>Computer = lnsa18, User = TRICS
+<DD>Computer = trics, User = trics
 <DT>HRPT
-<DD>Computer = lnsa11, User = HRPT
+<DD>Computer = hrpt, User = hrpt
 <DT>FOCUS
-<DD>Computer = lnsa16, User = FOCUS
+<DD>Computer = focus, User = focus
 <DT>AMOR
-<DD>Computer = lnsa14, User = AMOR
+<DD>Computer = amor, User = amor
 <DT>TASP
-<DD>Computer = tasp, User = TASP
+<DD>Computer = tasp, User = tasp
 <DT>POLDI
-<DD>Computer = poldi, User = POLDI
+<DD>Computer = poldi, User = poldi
 </dl>
-For starting the SICS server type <b>startsics</b>. This is a shell script
-which will starts all necessary server programs. This script works only on
-the instrument computer and in the appropriate instrument account.
+The SICS server process are controlled through the monit program. Usually the monit
+ daemon is running. If not, for instance after a reboot, it can be
+ started by typing <b>monit</b> at the unix prompt logged in as the
+ instrument user. Further monit commands:
+<dl>
+<dt> monit start target
+<dd>start the monit surveyed process target. For the choice of targets
+see below.
+<dt> monit stop target
+<dd>stops the monit surveyed process target. For the choice of targets
+see below.
+<dt> monit restart target
+<dd>restart the monit surveyed process target. Possible targets are:
+<dl>
+<dt>sicsserver
+<dd>The SICServer
+<dt>SerPortServer
+<dd>The serial port control program
+<dt>sync
+<dd>The file synchronisation program. This is responsible for coyping
+data files to the common AFS area. 
+<dt>simserver
+<dd>Only on TASP: a simulation SICS server 
+<dt>all
+<dd>Stop all processes
+</dl>
+<dt>monit status
+<dd>prints a status listing of everything watched by monit 
+<dt>monit quit
+<dd>Stops monit itself
+</dl>
+Stopping  everything thus involves two commands:
+<ul>
+<li> monit stop all
+<li> monit quit
+</ul>
+Restarting after this involves:
+<ul>
+<li>monit
+</ul>
+The older command startsics and killsics are still working and operate
+on the monit daemon as of now.
 </p>
 <p> 
 If all this does not help look under <a href="trouble.htm">trouble shooting