CA puts to disabled record

Bug #541090 reported by Andrew Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Base
Fix Released
Medium
Andrew Johnson

Bug Description

If a CA client issues a put to a disabled record then, when the record is enabled, database puts to the record will not make the record process until a CA put is again issued.

Original Mantis Bug: mantis-2
    http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=2

Tags: db 3.13
Revision history for this message
Andrew Johnson (anj) wrote :

The fix is:

diff -c -r1.89.4.6 dbAccess.c
*** dbAccess.c 2002/04/08 14:40:59 1.89.4.6
--- dbAccess.c 2002/05/02 20:09:15
***************
*** 607,612 ****
--- 607,613 ----
                if(*ptrace) printf("disabled: %s\\n",precord->name);
                /*take care of caching and notifyCompletion*/
                precord->rpro = FALSE;
+ precord->putf = FALSE;
                if (precord->ppn) dbNotifyCompletion(precord);
                /* raise disable alarm */
                if (precord->stat==DISABLE_ALARM) goto all_done;

Revision history for this message
Andrew Johnson (anj) wrote :

Fixed in R3.13.7

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.