Experimental Physics and Industrial Control System
Hi Jack,
On 2012-11-27 Jack Smith wrote:
> According to EPICS R3.14 Channel Access Reference Manual [1], I think
> caRepeater is only needed when multiple CA clients (CSS, EDM, etc.)
> run on the same host. Why should multiple IOC applications on the same
> Linux host be using caRepeater?
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
--
Computer science is as much about computers as astronomy is about
telescopes. -- Edsger Dijkstra
- Replies:
- Re: caRepeater object code not cross-compiled in R3.14.12.2 Jack Smith
- 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
- Navigate by Date:
- Prev:
Re: caRepeater object code not cross-compiled in R3.14.12.2 Jack Smith
- Next:
Re: posix osiSpawnDetachedProcess inherits scheduling policy + priority Andrew Johnson
- 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 Jack Smith
- Next:
Re: caRepeater object code not cross-compiled in R3.14.12.2 Jack Smith
- 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