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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | TRAPWRITE and logging CA_PUT activity |
From: | Vladimir Sirotenko <[email protected]> |
To: | [email protected] |
Date: | Fri, 16 Sep 2005 12:11:27 -0500 |
Hi,
Can anyone answer the following question: is
mechanism to log ca write activity implemented in 3.14 base epics release?
According to documentation, it is supposed to
( http://www.aps.anl.gov/asd/controls/epics/EpicsDocumentation/ReleaseNotes/ReleaseNotes3.13.4.html :
"The purpose of this new
facility is to allow things like logging Channel Access writes. Epics base
itself does not provide this ability but only the hook needed by such a
facility. DESY has developed a facility that logs CA puts. The trap writes
feacure allows the DESY facility to be implemented without any changes to epics
base. In addition it allows the user to decide what should be logged. This new
facility will be described in more detail in the 3.14 version of the Application
Developer's Guide."
but if I just look for the presence of
environmental name EPICS_IOC_CA_PUT_LOG_INET or as was suggested by V.Korobov
name which is supposed to be used in later CA_PUT release:
EPICS_IOC_LOG_CONFIG_FILE_NAME, then both are missing in src directory of the
epics base 3.14.6
Does anyone use such tools? And how?
Thanks,
Vladimir
|