(WP 4287)

Related alogs: 8600, 8475, 8294, 8207, 8200, 8164, 8076, 8055, 7768

I'm trying to see if the dust monitor IOC crashes are due to the virtual terminals hosted by 'screen'. To this end I am trying 'procServ' instead. I stopped the IOCs running in 'screen' on h0epics and started them with 'procServ'.

Equivalent commands:

As controls on h0epics:

cd /ligo/home/patrick.thomas/epics/iocs/dust/dust_met_one_227b_comp_ctrl/iocBoot/ioch0_dust_lvea
procServ -q --noautorestart -n "h0dustlvea" 20000 ../../bin/linux-x86_64/dust st.cmd

cd /ligo/home/patrick.thomas/epics/iocs/dust/dust_met_one_227b_comp_ctrl/iocBoot/ioch0_dust_lab
procServ -q --noautorestart -n "h0dustlab" 20001 ../../bin/linux-x86_64/dust st.cmd

cd /ligo/home/patrick.thomas/epics/iocs/dust/dust_met_one_227b_comp_ctrl/iocBoot/ioch0_dust_ey
procServ -q --noautorestart -n "h0dustey" 20002 ../../bin/linux-x86_64/dust st.cmd

cd /ligo/home/patrick.thomas/epics/iocs/dust/dust_met_one_227b_comp_ctrl/iocBoot/ioch0_dust_ex
procServ -q --noautorestart -n "h0dustex" 20003 ../../bin/linux-x86_64/dust st.cmd

cd /ligo/home/patrick.thomas/epics/iocs/dust/dust_met_one_227b_comp_ctrl/iocBoot/ioch0_dust_dr
procServ -q --noautorestart -n "h0dustdr" 20004 ../../bin/linux-x86_64/dust st.cmd

As controls on opsws1:

cd /ligo/cds/lho/h0/burt/2013/11/19/11:00
burtwb -f h0dustlvea.snap 
burtwb -f h0dustlab.snap 
burtwb -f h0dustey.snap   
burtwb -f h0dustex.snap 
burtwb -f h0dustdr.snap