From d56ca7f02ecf1043134ab63c239c76d7b14fdd7f Mon Sep 17 00:00:00 2001 From: Marty Kraimer Date: Tue, 18 Sep 2001 15:49:53 +0000 Subject: [PATCH] changes for R3.13.5 --- RELEASE_NOTES.html | 116 ++++++++++++++++++++++++++++++++------------- 1 file changed, 84 insertions(+), 32 deletions(-) diff --git a/RELEASE_NOTES.html b/RELEASE_NOTES.html index 71e8e7b80..319a4f39c 100644 --- a/RELEASE_NOTES.html +++ b/RELEASE_NOTES.html @@ -9,14 +9,52 @@

EPICS Release 3.13.5

-

June 2001

+

Sept 2001

Changes since 3.13.4

+convertRelease and checkRelease +

+New applications created with makeBaseApp.pl now have the functionality of +the makeConfigAppInclude.pl and makeIocCdCommands.pl scripts combined into +a single convertRelease.pl script. +

+The new script also provides consistency checking of the entries in the +config/RELEASE file, so that gnumake will stop with an error report if a +definition in any other <supporttop>/config/RELEASE file is different to +the same definition in this application. This checking can be disabled by +editing config/Makefile.Host. +

+Applications created using earlier versions of EPICS will continue to work +as before and will not benefit from the consistency check functionality. +

+devAiSoftRaw and devAoSoftRaw +

+ai and ao records using DTYP="Raw Soft Channel" can have their EOFF +and ESLO fields set manually at design or run-time, and these values will +be used when LINR=LINEAR. The same applies to any device support that +doesn't provide a special_linconv() routine; if special_linconv() is +provided however, the original behaviour occurs (EOFF is set to EGUL and +ESLO is calculated by that routine). The ESLO and EOFF fields now have CA +monitors posted if their value is changed by the special_linconv() +routine. +

+cac_recv_task +

+Increased stack size from 4096 to 819l. +

+drvTS +

+Now uses osiSock for to handle implementation diffences +

Constant Links

Hex and octal constants are now accepted for constant links. +recGblInitConstantLink uses %i instead of %u for unsigned types. +This is so that hex constants are accepted. %u does not accept hex. +dbPutString makes a link constant if either strtod or strtol eats entire string. +Previously only strtod was used.

Breakpoint tables

@@ -338,48 +376,62 @@ involved the year 00 appeared in the ascii string

Channel Access

-

The CA comments are from Jeff Hill.

+

+1) A severe problem where the CA client did not exit a loop sending UDP to a list of addresses +if an error condition was returned from the system call which sends a UDP frame was fixed. +This problem was discovered during load testing, and will be more likely to occur under heavy +network loading conditions. +

-

1) I fixed a severe problem where the CA client did not exit a loop sending -UDP to a list of addresses if an error condition was returned from the system -call which sends a UDP frame. This problem was discovered by me during heavy -load testing, and if
-it occurs in an operational system it will probably be occurring under heavy -network loading conditions.

+

+2) A problem where the client library could fail and use a deallocated data structure if a +connection dropped while it was waiting to send a message to a client was fixed. +

-

2) I fixed a problem where the client library could fail and use a -deallocated data structure if a connection dropped while it was waiting to -send a message to a client.

+

+3) The CA client now maintains a congestion avoidance threshold on UDP search +transmissions similar to the congestion avoidance algorithm employed by modern version of +TCP. There are also some small changes related to how the search counters are maintained +without allowing them to overflow. This patch was made in R3.13.1 because I originally +identified it as the fix for (1) above, but it turned out to not be the root cause. +

-

3) The CA client now maintains a congestion avoidance threshold on UDP -search transmissions similar to the congestion avoidance algorithm employed by -modern version of TCP. There are also some small changes related to how the -search counters are maintained without allowing them to overflow. This patch -was made in R3.13.1 because I originally identified it as the fix for (1) -above, but it turned out to not be the root cause.

+

+4) A bug fix was made for a problem where the CA repeater was inheriting on HP-UX, and +possibly other UNIX systems that are not Solaris, certain open file descriptors when +fork()/exec() are used to start the CA repeater. +

-

4) A bug fix was made for Ralph Lange's problem where the CA repeater was -inheriting on HP-UX, and possibly other UNIX systems that are not Solaris, -certain open file descriptors when fork()/exec() are used to start the CA -repeater.

+

+5) Changes that allow CA to work on Microsoft Visual C++ 6.0 (which includes a new win +sock DLL and some changes in esoteric parts of the socket API). +

-

5) Changes that allow CA to work on Microsoft Visual C++ 6.0 (which -includes a new win sock DLL and some changes in esoteric parts of the socket -API).

+

+6) always inform client of "no write access" for a SPC_NOMOD fields. +

-

6)  always inform client of "no write access"  for a SPC_NOMOD fields.

+

+7) calls to ca_printf removed from rsrv. +

-

7) calls to ca_printf removed from rsrv.

+

+8) prevent UDP daemon from running damaged messages with TCP protocol and +visa-versa +

-

8) prevent UDP daemon from running damaged messages with TCP protocol and -visa-versa

+

+9) use ipAddrToA() so that address print out does not come out byte swapped on the PC +

-

9) use ipAddrToA() so that address print out does not come out byte swapped -on the PC

+

+10) improved debug messages and added diagnostics +

-

10) improved debug messages and added diagnostics

+

+11) don't send an exception to client when bad request received over UDP. +

-

11)  dont send an exception to client when bad request received over udp.