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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: problem about environment variables under vxWorks-6.6 |
From: | "Jeff Hill" <[email protected]> |
To: | "Andrew Johnson" <[email protected]> |
Cc: | [email protected] |
Date: | Thu, 11 Jun 2009 18:44:33 -0600 |
Andrew, This is a 2nd try – this time clipping
out Gongfa Liu’s original message which may be triggering some behavior
in the mail system. Jeff ------------------snip-snip------------- 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? ------------------snip-snip------------- Jeff |