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
- References:
- Launching CS-Studio BOY screens tom.cobb
- Re: Launching CS-Studio BOY screens Andrew Johnson
- Re: Launching CS-Studio BOY screens Michael Davidsaver
- Navigate by Date:
- Prev:
Re: How to tag soft channels as undefined/disconnected Kellee Summers
- Next:
Re: Launching CS-Studio BOY screens Hu, Yong
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Launching CS-Studio BOY screens Hu, Yong
- Next:
New to EPICS - system design questions Ryan Pierce
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|