Symptom: CA clients on all versions of EPICS with unresolved channels +broadcast search messages too frequently if an EPICS R3.13.3 server is +present. This bug does not occur if an R3.13.3 server is not present. +
Changed: CA server now sends beacon messages which uniquely identify +the server address. The CA repeater was also upgraded to detect, and fix, +any problems of this nature. +
Symptom: Undefined symbols show up when EPICS R3.13.3 was loaded +into a PC IOC running Tornado II. +
Changed: Conditionally compiled out references to architecture inappropriate
+system calls.
+
+
dfanoutRecord
+
+
These did not properly set monitors when delta=0x80000000. This happened +when the record was attached to a 32 bit digital device . +
Access Security TrapWrite feature +
Access security now provides the ability to trap write requests coming +from a client. RULEs in the access configuration files accept an option +argument NOTRAPWRITE or TRAPWRITE. For example: +
RULE(1,WRITE,TRAPWRITE)+If the additional argument is not specified the default is NOTRAPWRITE. +
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. +
dbAccess +
When obtaining graphic, control, and alarm limits, the destination values +were not initialized. If record support did not set values then the unitialized +values were returned. This caused exceptions to occut on powerPCs. The +values are now initialized to 0. +
drvTS.c
+
+