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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | security rules and autosave |
From: | Touchard Dominique <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Tue, 22 Jul 2014 12:25:41 +0000 |
Hi,
I need some advices on rules and autosave. I configured a Linux IOC with following rules ================================================================ ASG(FAISCEAU) { #Operation mode lock INPA(DEFAULT:OPState) #BEAM characteristics lock INPB(FAISCEAU:WritePerm) # We can always read PVs RULE(1,READ) # BEAM Characteristcs could be changed by everyone in maintenance mode and BEAM characteristics unlocked RULE(1,WRITE) { CALC("A=0 && B=1") } # BEAM Characteristcs could be changed only by operators in operation mode and BEAM characteristics unlocked RULE(1,WRITE) { UAG(operateurs) CALC("A=1 && B=1") } } ============================================================== DEFAULT:OPState could be 0:Maintenance 1:Operation FAISCEAU:WritePerm could be 0:BEAMLocked 1:BEAMUnlocked These rules work perfectly when values of DEFAULT:OPState and FAISCEAU:WritePerm are changed manually. At starting, with autosave mechanisme, there is a mismatch between right access and lock values. Any ideas? Dominique. |