Experimental Physics and
Industrial Control System

----- Original Message -----

From: Ralph Lange

To: Vladimir Sirotenko

Cc: [email protected]

Sent: Friday, September 16, 2005 12:40 PM

Subject: Re: TRAPWRITE and logging CA_PUT activity

Hi Vladimir,

It's exactly as you were citing from the Release Notes:

EPICS Base itself does not provide this ability, but only the hook needed by such a facility.
This new hook facility is described in more detail in the 3.14 Application Developer's Guide, in chapter 8.8 ("Trapping Channel Access Writes").

Documentation on the DESY "CA Put Logging" module, which can be hooked into this facility, can be found on the DESY page that can be reached from the "Extensions" page of the EPICS Web (section "Other Tools or Libraries").

There are no plans to include such plug-in modules into EPICS Base.

Hope this helps,
Ralph


Vladimir Sirotenko wrote:

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