RESTART PROCEDURES FOR TOF RATES/TDC SPECTRA

The software which enables display of TOF/VETO rates and
on web ( http://h1tofpc2.desy.de) and on Lumi applet 
(via h1lumiserver, which sends also data to HERA via Nextmex), 
rates and TDC spectra in TofMon consist of the following:


1) rate server: process running on VME single board computer
 (skyros.desy.de) in rack O4. The process should be started 
 manually after the VME crate was switched off. Please restart
 "lograte" process on h1tofpc2 after restart of the server.

 To check whether processes are running use:
   logon as vdodo on skyros.desy.de
   ps x | grep rate2 | grep -v grep
   (there should be N_connections + 2 processes with name rate2)

 To stop rate server:
   logon as vdodo on skyros.desy.de
   ps x        (note "pgrp" of processes with name ./rate2)
   kill pgrp   (or kill -9 PIDs)
   Wait 5 seconds
   Check rate2 processes again: "ps x", if there are still
   processes with name rate2 then "kill -9" all of them.

 To start rate_server:
   logon as vdodo on skyros.desy.de
   . ~/rate/RUN2
   
   Make sure that within few minutes Lumi Java client connects 
   to the server: run "netstat" command and look for the line
   "tcp  0  0  skyros.desy.de.8010  h1lumiserver.des.53906  ESTABLISHED"
   If there are no connection then call Lumi expert (Igor Cheviakov
   tel. 3404) and ask him to restart client, otherwise "e-Bkgd" and 
   "p-Bkgd" curves on Lumi display in Room 301 and in HERA control room
   will be frozen.


2) p-spike server: process running on VME single board computer
 (skyros.desy.de) in rack O4. The process should be started 
 manually after the VME crate was switched off. Please restart
 "dumpsike" process on h1tofpc2 after restart of the server.

 To check whether processes are running use:
   logon as vdodo on skyros.desy.de
   ps x | grep rate4 | grep -v grep
   (there should be N_connections + 2 processes with name rate4)

 To stop spike server:
   logon as vdodo on skyros.desy.de
   ps x        (note "pgrp" of processes with name ./rate4)
   kill pgrp   (or kill -9 PIDs)
   Wait 5 seconds
   Check rate4 processes again: "ps x", if there are still
   processes with name rate4 then "kill -9" all of them.

 To start spike server:
   logon as vdodo on skyros.desy.de
   cd ~/spike
   ./ptl +ptl_al1.cfg
   Press Ctrl-C when bunch of digits are printed
   . RUN4
   

3) TDC/PTL server: process running on VME single board computer
 (ararat.desy.de) in rack M6. The process should be started 
 manually after the VME crate was switched off.

 To check whether processes are running:
   logon as vdodo on ararat.desy.de
   ps x | grep tdcsrv | grep -v grep
   (there should be N_connections + 2 processes with name tdcsrv)

 To stop server:
   logon as vdodo on ararat.desy.de
   ps x        (note "pgrp" of processes with name ./tdcsrv)
   kill pgrp   (or kill -9 PIDs)
   Wait 5 seconds
   Check tdcsrv processes again: "ps x", if there are still
   processes with name tdcsrv then "kill -9" all of them.

 To start server:
   logon as vdodo on ararat.desy.de
   login bma
   . ~/tdcsrv/RUN


4) FNC trigger elements
 FNC trigger elements are sent to Central Trigger via
 one PTL2000 module in VME crate in rack M6. After switching
 on/off the VME crate the PTL2000 module should be programmed:
   logon as vdodo on ararat.desy.de
   ~/fnc/ptl_load
   

5) Nextmex client which maintains HERA beam currents
 in shared memory which is used by "lograte". The process
 name is mexcln, it should be running on h1tofpc2.

 To check whether process is running use:
   ps x | grep mexcln | grep -v grep
   You can run also ./showcurr (exit via Ctrl-C) -- the program 
   shows beam currents in shared memory). The currents/lifetime 
   should be updating.

 To start beam currents client:
   login as h1tof on h1tofpc2
   cd /x01/usr/h1tof/nextmex
   nohup mexcln 0 0 1 </dev/null &

 To stop beam currents client:
   login as h1tof on h1tofpc2
   kill -USR1 `ps x | grep mexcln | grep -v grep`
   (or kill -9 `ps x | grep mexcln | grep -v grep`)


6) TOF/VETO rate logging process: lograte, running on
 h1tofpc2.

 To check whether process is running use:
   login as h1tof on h1tofpc2
   ps x | grep lograte | grep -v grep

 To stop rate logging process:
   login as h1tof on h1tofpc2
   kill -9 `ps x | grep lograte.com | grep -v grep`
   killall lograte  (or killall -9 lograte)

 To start rate logging process:
   login as h1tof on h1tofpc2
   cd /x01/usr/h1tof/rate
   nohup lograte.com >/dev/null 2>&1 &


7) p-spike logging process: dumpspike, running on
 h1tofpc2.

 To check whether process is running use:
   login as h1tof on h1tofpc2
   ps x | grep dumpspike | grep -v grep

 To stop spike logging process:
   login as h1tof on h1tofpc2
   killall dumpspike  (or killall -9 dumpspike)

 To start spike logging process:
   goto the room 301 in North Hall
   locate TOF PC at A3RT
   Switch to second KDE panel: press Ctrl-F2
   Press Ctrl-C in the xterm window
   cd ~/spike
   . DUMPSPIKE
   Switch back to 1st KDE panel: press Ctrl-F1



After VME crate in O4 was powered off/on:
 1) stop lograte process (item 6 above)
 2) stop dumpsike process (item 7 above)
 3) start rate server (item 1 above)
 4) start spike server (item 2 above)
 5) start lograte process (item 6 above)
 6) start dumpsike process (item 7 above)
 7) restart TofMon in room 301

After VME crate in M6 was powered off/on:
 1) start TDC server (item 3 above)
 2) program FNC PTL2000 (item 4 above)
 3) restart TofMon in room 301

After h1tofpc2 was rebooted/powered off:
 1) start mexcln process (item 5 above)
 2) start lograte process (item 6 above)
 3) start dumpsike process (item 7 above)
 4) Start TofMon in room 301


There are also several cron jobs which update
preselected www views. They are started
automatically. See "crontab -l" output.
crontab file is in /x01/usr/h1tof/rate/crontab.

The web server (apache) running on h1tofpc2 under 
root acount. Started automatically during PC boot.
or ("rcapache stop; rcapache start" under root)
Copy of the nominal config file for httpd --
/etc/httpd/httpd.conf is in /x01/usr/h1tof/rate/.