Epics Logger Scripts for SBS

From Hall A Wiki
Revision as of 17:35, 23 October 2022 by Rom (Talk | contribs) (How to Add Variables to EPICS logging for SBS)

Jump to: navigation, search

Here is some technical information about how to add EPICS variables to the logging of information for the SBS.

Explaining the EPICS logging scheme for SBS

How to Add Variables to EPICS logging for SBS

1. Edit EpicsToFile, add your variable.
2. Might want run this with TESTPRINT=1 and run EpicsToFile interactively to check it.  Don't forget to restore TESTPRINT=0.
3. Kill the current running of EpicsToFile

[sbs-onl@adaq1 halla]$ ps awx | grep EpicsToFile
 4018 pts/69   S+     0:00 grep --color=auto EpicsToFile
10161 ?        S      1:03 /bin/ksh /adaqfs/home/sbs-onl/logentry_scripts/halla//EpicsToFile

kill -9 10161

4. Then wait.  The cron script "startCron" will restart it in a few minutes.  Perhaps check the process list to be sure.

One fly in the ointment at the moment is that if someone is doing "less EpicsToFile" or "more EpicsToFile" on adaq1, then unfortunately startCron is not smart enough to restart EpicsToFile. It is smart enough to ignore emacs sessions. In the meantime, kill the "less" command, too.

[sbs-onl@adaq1 halla]$ ps awx | grep EpicsToFile
 2312 pts/69   T      0:00 less EpicsToFile
 3034 pts/69   S+     0:00 grep --color=auto EpicsToFile
10161 ?        S      1:04 /bin/ksh /adaqfs/home/sbs-onl/logentry_scripts/halla//EpicsToFile

kill -9 2312
kill -9 10161

back to https://hallaweb.jlab.org/wiki/index.php/Epics_Logger_Scripts_for_SBSba

How to add a variable

1. Edit EpicsToFile, add your variable.
2. Might want run this with TESTPRINT=1 and run EpicsToFile interactively to check it.  Don't forget to restore TESTPRINT=0.
3. Kill the current running of EpicsToFile

[sbs-onl@adaq1 halla]$ ps awx | grep EpicsToFile
 4018 pts/69   S+     0:00 grep --color=auto EpicsToFile
10161 ?        S      1:03 /bin/ksh /adaqfs/home/sbs-onl/logentry_scripts/halla//EpicsToFile

kill -9 10161

4. Then wait.  The cron script "startCron" will restart it in a few minutes.  Perhaps check the process list to be sure.

One fly in the ointment at the moment is that if someone is doing "less EpicsToFile" or "more EpicsToFile" on adaq1, then unfortunately startCron is not smart enough to restart EpicsToFile. It is smart enough to ignore emacs sessions. In the meantime, kill the "less" command, too.

[sbs-onl@adaq1 halla]$ ps awx | grep EpicsToFile
 2312 pts/69   T      0:00 less EpicsToFile
 3034 pts/69   S+     0:00 grep --color=auto EpicsToFile
10161 ?        S      1:04 /bin/ksh /adaqfs/home/sbs-onl/logentry_scripts/halla//EpicsToFile

kill -9 2312
kill -9 10161