Experimental Physics and
Industrial Control System

Ralph Lange <[email protected]> · Wed, 11 Jul 2007 16:43:15 +0200

Hello -

part of a proper "professional" soft IOC setup is having a PID file that

the system scripts can use to selectively start/stop soft IOCs as

required. Through multiple forks, shells and a screen session, it is

hard to determine the PID of the soft IOC from the startup script. My

solution was exporting an environment variable PIDFILE into that chain

of fork/shell/screen and have the soft IOC itself create the PID file,

if that environment variable is set.

http://www.aps.anl.gov/epics/wiki/index.php/How_to_Set_Up_a_Soft_IOC_Framework_on_Linux#Make_the_Soft_IOC_Create_the_PID_File

shows the code I added to my soft IOCs.

Does anyone see any possible side-effects? Would that code be

Windows-proof? Should I integrate it into the example stuff in base to

make it standard?

Regards,
Ralph