From 7370a230538e968e0059be7248b5a2bba0d9748d Mon Sep 17 00:00:00 2001 From: Andrew Johnson Date: Mon, 29 Aug 2005 19:42:11 +0000 Subject: [PATCH] Described the new dbRecordsOnceOnly variable, originally requested by the BCDA group. --- documentation/RELEASE_NOTES.html | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index a8f3cac60..2b4b58ede 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -13,8 +13,7 @@

Changes since 3.14.7

drvTS

- -This is removed from EPICS base. The version that previously came with base +

This is removed from EPICS base. The version that previously came with base was the version that worked with the APS event system. It is available from APS. The version that works with the newer event systems that evolved from the APS system is available from the Swiss Light Source.

@@ -30,6 +29,7 @@ It was possible to call taskwdInsert before the threadid was actually set.

dbLockGetLockId incorrectly always returned 0. dbBkpt (database breakpoint facility) is the only code that needed this. This caused unknown errors if the dbBkpt facility is used.

+

gpHashLib.c

The maximum size was initialized to 65636 instead of 65536.

@@ -40,7 +40,6 @@ if the dbBkpt facility is used.

iocsh

I/O redirection from vxWorks startup scripts now works.

-

RTEMS

Set POSIX TZ environment variable from NVRAM, or failing that, from EPICS_TIMEZONE.

Cleaned up support for obtaining network configuration from NVRAM.

@@ -56,6 +55,17 @@ server required.

Builds on Tiger.

Readline now used by default.

+

dbRecordsOnceOnly

+

This new variable which can be controlled using the iocsh var +command (or by simple assignment in the vxWorks shell) allows users to change +the behaviour of dbLoadRecords() when it finds a duplicate record +definition. The default behaviour has always been to permit multiple record() +statements for the same record name when loading record instances, but by +setting dbRecordsOnceOnly to any non-zero value, duplicates will +instead generate an error message instead. It is expected that this will only +be used in special circumstances, to detect the presence of unintentional +duplicates where it is known that they should not exist.

+

EPICS Base Release 3.14.7
7 December 2004