> Recall that if this is 3.14.10 on a little-endian
> architecture (e.g.Intel) then there is a bug that
> causes this message:
> "The CA server's beacon address list was empty
> after initialization?"
>
> if EPICS_CA_AUTO_ADDR_LIST=NO
Mark is correct. The details, including a patch, are in entry 331 in the
EPICS bug tracking system.
Jeff
> -----Original Message-----
> From: Mark Rivers [mailto:[email protected]]
> Sent: Monday, June 15, 2009 8:28 PM
> To: Jeff Hill; Andrew Johnson
> Cc: [email protected]
> Subject: RE: problem about environment variables under vxWorks-6.6
>
> Jeff,
>
> Recall that if this is 3.14.10 on a little-endian architecture (e.g.
> Intel) then there is a bug that causes this message:
> > "The CA server's beacon address list was empty after initialization?"
>
> if EPICS_CA_AUTO_ADDR_LIST=NO
>
> Mark
>
>
>
> -----Original Message-----
> From: [email protected] on behalf of Jeff Hill
> Sent: Thu 6/11/2009 7:36 PM
> To: Andrew Johnson
> Cc: [email protected]
> Subject: FW: problem about environment variables under vxWorks-6.6
>
>
> Andrew,
>
> I sent this message to tech-talk ([email protected]) some time back
> but maybe it didn't go through. I am suspicious because I sent another one
> later and it did go through (so this isn't maybe a delay related issue).
>
> Jeff
>
> -----Original Message-----
> From: Jeff Hill [mailto:[email protected]]
> Sent: Thursday, June 11, 2009 5:45 PM
> To: 'EPICS tech-talk'
> Subject: RE: problem about environment variables under vxWorks-6.6
>
>
> > "The CA server's beacon address list was empty after initialization?"
>
> If EPICS_CA_AUTO_ADDR_LIST is set to YES (the default) then the beacon
> address list is auto-configured using each of the network interfaces
> present on the local host. When fetching EPICS_CA_AUTO_ADDR_LIST, if
> envGetConfigParam returns a nill pointer, the server will decide to auto
> configure the beacon address list. So perhaps there is a 2nd possibility
> which might be that the system in question doesn't have any operable
> network interfaces installed?
>
> Jeff
>
> > -----Original Message-----
> > From: [email protected] [mailto:tech-talk-
> [email protected]]
> > On Behalf Of Andrew Johnson
> > Sent: Thursday, June 11, 2009 3:34 PM
> > To: EPICS tech-talk
> > Subject: problem about environment variables under vxWorks-6.6
> >
> > This message is from Gongfa Liu, I'm forwarding it while the APS
> sysadmins
> > figure out why all email from DESY is being caught as spam... -
> Andrew
> >
> > ----------------------------------------------------------
> >
> > Hi, all,
> >
> > I created an ioc application with makeBaseApp.pl for test under the
> > following environment:
> > epics base: 3.14.10
> > vxWorks: 6.6
> > target architecture: vxWorks-pentium
> >
> > I got a waring message after iocInit:
> > "The CA server's beacon address list was empty after initialization?"
> >
> > This waring message is from ~base/src/rsrc/online_notify.c, I use
> > epicsEnvShow(NULL) and epicsPrtEnvParams() to print the environment
> > variables at the position where the warning message is created, but
> > nothing is printed. It seems that the environment variables set is not
> > inherited. What is missing in the vxWorks image? Any suggestions are
> > appreciated.
> >
> > Thank you.
> > Gongfa Liu
> >
> > --
> > ----------------------------------------------------------
> > Gongfa Liu MKS-2, DESY
> > phone: +49-40-8998-1642 Notkestr. 85
> > fax: +49-40-8998-4388 22607 Hamburg
> > e-mail: [email protected] Germany
> > ----------------------------------------------------------
>
- References:
- FW: problem about environment variables under vxWorks-6.6 Jeff Hill
- RE: problem about environment variables under vxWorks-6.6 Mark Rivers
- Navigate by Date:
- Prev:
Controlling multiple CAN busses Elliott Wolin
- Next:
Pfeiffer Turbo Pump /controller Vesna Samardzic-Boban
- 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: problem about environment variables under vxWorks-6.6 Mark Rivers
- Next:
RE: problem about environment variables under vxWorks-6.6 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
|