Experimental Physics and
Industrial Control System

Kevin Peterson <[email protected]> · Wed, 13 Aug 2014 10:17:15 -0500

On 8/12/14, 9:00 PM, Michael Davidsaver wrote:
> We still haven't completely dealt with the shared workspace problem.  To
> mitigate this, our wrapper script keeps track of which computer a
> workspace is used from.  Attempts to start from a different machine give
> a prompt and the option to terminate the running session (via ssh).

I wrote a python script to handle the shared-workspace problem on linux:

https://subversion.xray.aps.anl.gov/bcdaext/cssboy_deployment/src/startCSS.py

The script is only useful under the following conditions:

1. opi files reside in projects outside of the CSS workspaces
2. CSS workspaces link to the external projects rather than copying them
into the workspace
3. All CSS workspaces are interchangeable

The script launches CSS with the first workspace it finds that is
available.  It doesn't give you any information about who is using a
given workspace.  The script expects the CSS_WORKSPACES env var to point
to the workspaces directory and CSS_BIN to point to css executable.

I usually designate the "Default" workspace as the master.  After all
the projects containing opis are added to it, I make additional copies
of the workspace for each of the instances of css that need to run
concurrently.

Kevin

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System