- Updated docs

SKIPPED:
	psi/utils/SerPortServer.c

doc/user/trouble.htm

@@ -71,6 +71,13 @@ The log files show you all commands given and all the responses of the system.
  safely ignored, SICS fixes this condition. 
 </dl>
 </p>
+<h2>Restarting SICS</h2>
+<p>
+All of SICS can be restarted through the command:
+<pre>
+monit restart all
+</pre>
+</p>
 <h2>Starting SICS</h2>
 <p>
 An essential prerequisite of SICS is that the server is up
@@ -79,7 +86,7 @@ fails. Only after a reboot or when the keepalive processes were killed (see
 below) the SICServer must be restarted. This is done for all instruments by
 typing: 
 <pre>
-startsics 
+monit
 </pre>
 at the command prompt. startsics actually starts two programs: one is
 the replicator application which is responsible for the automatic
@@ -95,9 +102,10 @@ everything  the server process must be killed. This can be accomplished either m
 </p>
 <h2>Stopping SICS</h2>
 <p>
-All SICS processes can be stopped through the command:
+All SICS processes can be stopped through the commands:
 <pre>
-killsics
+monit stop all
+monit quit
 </pre>
 given at the unix command line. You must be the instrument user 
  (for example DMC) on the instrument computer for this to work properly.
@@ -123,81 +131,40 @@ can not be resolved by simple means.
 <p>
 Sometimes it happens that the SICServer hangs while starting up or hardware
  components are not properly initialized. In such cases it is useful to
- look at the SICS servers startup messages. In order to do so, both the 
- SICServer and its keepalive process must be killed first. On the instrument
- acount issue the command:
+ look at the SICS servers startup messages. 
+ On the instrument account issue the commands:
 <pre>
-ps -A | grep SICS
+monit stop sicsserver
+cd inst_sics
+./SICServer inst.tcl | more
 </pre>
-A message like this will be printed:
+Replace inst with the name of the appropriate instrument in lower case.
+For example, from the home directory of the hrpt account on the computer hrpt:
 <pre>
-  23644 ??       I        0:00.00 ksh keepalive SICServer focus.tcl
- 23672 ??       R       59:24.05 SICServer focus.tcl
-  7119 ttyp6    S  +     0:00.00 grep SICS
+cd
+monit stop sicsserver
+cd hrpt_sics
+./SICServer hrpt.tcl | more
 </pre>
-Remember the numbers in the first columns (the PID's) and kill both 
- programs by issuing the command:
-<pre>
-kill -9 pid pid
-</pre>
-Example:
-<pre>
-kill -9 23644 23672
-</pre>
-Note, the numbers are those displayed with the ps -A command. 
-Then cd into the bin directory of the instrument account and issue 
- the unix command:
-<pre>
-SICServer inst.tcl | more
-</pre>
-Replace inst.tcl with the name of the appropriate instrument initialisation 
- file. This allows to page through SICS startup messages and will help to
+This allows to page through SICS startup messages and will help to
  identify the troublesome component. The proceed to check the component and
  the connections to it.
 </p>
 
-<h2>Getting New SICS Software</h2>
-<p>
-Sometimes you might want to be sure that you have the latest SICS software. 
-This is how to get it:
-<ol>
-<li>Login to the instrument account.
-<li>If you are no there type cd to get into the home directory. 
-<li>Type <b>killsics</b> at the unix prompt in order to stop the SICS server.
-<li>Type <b>sicsinstall exe</b> at the unix prompt for copying new
-  SICS software from the general distribution area.
-<li>Type <b> startsics</b> to restart the SICS software. 
-</ol>
-</p>
-<h2>Hot Fixes</h2>
-<p>
-When there is trouble with SICS you may be asked by one of the SICS 
- programmers to copy the most recent development reason of the SICS server
- to your machine. This is done as follows:
-<ol>
-<li>Login to the instrument account.
-<li>cd into the bin directory, for example: /home/DMC/bin.
-<li>Type <b> killsics</b> at the unix prompt in order to stop the SICS server.
-<li>Type <b>cp /data/koenneck/src/sics/SICServer .</b> at the unix prompt.
-<li>Type <b> startsics</b> to restart the SICS software. 
-</ol>
-<b>!!!!!! WARNING !!!!!!!. Do this only when advised to do so by a competent 
- SICS programmer. Otherwise you might be copying a SICS server in an 
- instable experimental state!</b>
-</p>
 <h2> HELP debugging!!!!</h2>
 <p>
 The SICS server hanging or crashing should not happen. In order to sort such
 problems out it is very helpful if any available debugging information is
 saved and presented to the programmers. Information available are the log
 files as written continously by the SICS server and posssible core files
-lying around. They have just this name: core. In order to save them create a
+lying around. They have just this name: core.pid, where pid is the process identification number.
+ In order to save them create a
 new directory (for example dump2077) and copy the stuff in there. This looks
 like:
 <pre>
 /home/DMC> mkdir dump2077
 /home/DMC> cp log/*.log dump2077
-/home/DMC> cp core dump2077
+/home/DMC> cp core.2077 dump2077
 </pre>
 The <tt>/home/DMC> </tt> is just the command prompt. Please note, that core
 files are only available after crashes of the server. These few commands