[email protected] wrote:
>
> This happened under such circumstances:
> At first I booted IOC with Access Sequrity disabled.
> Then on the IOC console I typed:
>
> asSetFilename("<my Access Sequrity configuration file>")
>
> and then:
>
> asInit
As documented in the Application Developer's guide, access security MUST
be started at iocInit (by having asSetFilename appear in startup file
before iocInit) or else it can not be started at all. The reason is that
there is no easy way to take care of the existing channel access
clients.
I looked and in beta11 it did try to start access security in your
situation.
Thus this was the bug that caused your problem
For next release this is fixed.
Marty Kraimer
- References:
- CA client suspend korobov
- Navigate by Date:
- Prev:
Postscript version of the record reference manual Bob Dalesio
- Next:
CA client suspend korobov
- 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:
CA client suspend korobov
- Next:
boot problems & related on hkbaja47 Maren Purves
- 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
|