I've come across a situation in which I have 20 iocs, each of which will have
a unique access security group with access conditioned on a local process
variable. The form of the 20 access security rules is the same. I have 2 choices
for handling this. Create 20 unique files each with a single access group, or
create 1 file that includes all 20 access groups. The first option's
disadvantage is it requires 20 files. The second's disadvantage is that each
ioc will create a channel access connection to the 19 pv's that are not local
even though the rules invoking those pvs are never used in the that ioc.
Not a pleasant thought. In this case, I'd get 19x20 or 380 superfluous channel
access connections. Sooo, for now, I'll just create a template and use subtool
it create 20 access security files.
It would have been real handy though, if asSetFilename supported macro
substitution. If that were so, I could defer macro substitution to the
start up command files. Anyway, I suggest that some future incarnation of
asSetFilename support macro substitution. Comments?
Frank
- Navigate by Date:
- Prev:
vxWorks stat through EPICS records Jim B. Kowalkowski
- Next:
Bug in OMS Driver routines Guy Jennings
- 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:
vxWorks stat through EPICS records Jim B. Kowalkowski
- Next:
Bug in OMS Driver routines Guy Jennings
- 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
|