On Mon, 2007-10-01 at 15:47 -0600, Jeff Hill wrote:
> Starting with EPICS R3.14.7 this maximum search rate interval plateau in
> seconds is determined by the EPICS_CA_MAX_SEARCH_PERIOD environment
> variable.
>
That's an interesting feature
> Beacon anomalies are detected by the client library (in the client
> application's process). The repeater daemon is just a fan-out engine.
ok
> The client subscribes with the CA repeater using the EPICS_CA_REPEATER_PORT
> it is configured with.
Ok, so possibly I have several caRepeater because the
EPICS_CA_REPEATER_PORT was not the same when the client were started.
> The server sends beacons to the address list configured by
> EPICS_CAS_AUTO_BEACON_ADDR_LIST and EPICS_CAS_BEACON_ADDR_LIST. If ports are
> not configured there, then they are specified by EPICS_CAS_BEACON_PORT.
>
According to a previous thread,
http://www.aps.anl.gov/epics/tech-talk/2007/msg00273.php
the EPICS_CAS_* environment variables are only for "new CAS server".
So when I build my IOC servers are they running on the new or the old CA
server libraries?
--
E
- Replies:
- RE: Beacon and caRepeater Jeff Hill
- References:
- Beacon and caRepeater Emmanuel Mayssat
- RE: Beacon and caRepeater Jeff Hill
- Navigate by Date:
- Prev:
RE: Beacon and caRepeater Jeff Hill
- Next:
RE: Beacon and caRepeater Jeff Hill
- 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: Beacon and caRepeater Jeff Hill
- Next:
RE: Beacon and caRepeater Jeff Hill
- 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
|