Hi Andrew,
>On Tue, Nov 27, 2012 at 3:24 PM, Andrew Johnson <[email protected]> wrote:
>
> An IOC is a CA client as well as being a server: record links often point to
> records on other IOCs, the Access Security mechanism may subscribe to channels
> on other servers, and any sequence programs running in the IOC also use CA.
> The caRepeater is looked for and if necessary started at iocInit even if the
> CA client library never actually has to make any external connections because
> all of the PV names requested can be found locally within the IOC.
>
> - Andrew
>
Thanks for your detailed explanation.
I am trying to look through base-3.14.*/src/misc/iocInit.c. I guess
the only function related to caRepeater would be rsrv_init(). Then I
take a quick look at src/rsrv/caservertask.c, but still don't see how
the caRepeater get spawned. Could you tell me how the caRepeater is
started during iocInit? Also what does "rsrv" mean / stand for?
Thanks again,
Jack
- Replies:
- Re: caRepeater object code not cross-compiled in R3.14.12.2 Ralph Lange
- Re: caRepeater object code not cross-compiled in R3.14.12.2 Andrew Johnson
- References:
- caRepeater object code not cross-compiled in R3.14.12.2 Rod Nussbaumer
- Re: caRepeater object code not cross-compiled in R3.14.12.2 Jack Smith
- Re: caRepeater object code not cross-compiled in R3.14.12.2 Andrew Johnson
- Navigate by Date:
- Prev:
Re: Several soft IOCs on one host Kasemir, Kay
- Next:
Re: caRepeater object code not cross-compiled in R3.14.12.2 Ralph Lange
- 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: caRepeater object code not cross-compiled in R3.14.12.2 Andrew Johnson
- Next:
Re: caRepeater object code not cross-compiled in R3.14.12.2 Ralph Lange
- 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
|