TO DO List for Nerses: Difference between revisions
Jump to navigation
Jump to search
initial item list; softioc startup configs |
|||
Line 29: | Line 29: | ||
== O classc2 recovery == | == O classc2 recovery == | ||
We suspect something wrong with scalers. | |||
== O IOC Logging setup == | == O IOC Logging setup == |
Revision as of 08:47, 27 September 2007
Finished items marked by X, open items by O.
O Driver support for CAEN board 1932
X Software IOC startup configurations
The software IOC-es are running on:
clonpc1 - gamma and tpe profilers clonpc2 - HV of beam line devices (hvDvcs CAEN MF) clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)
Startup directories now are $IOC/`hostname -s`. These files are used:
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1: envPaths softioc.pipe startup.all /usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2: envPaths softioc.pipe startup.all /usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3: envPaths softioc.pipe startup.all
Startup script is /etc/init.d/softioc and it is different for each compter. Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore. To protect softioc.pipe files they made with read-only permissions.
O classc2 recovery
We suspect something wrong with scalers.