5.7.1.2 Lock Sets

Bug #1800714 reported by Andrew Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Application Developers' Guide
New
Undecided
Unassigned

Bug Description

Tim Gaggstatter (Gemini) wrote:

Reading through the EPICS AppDevGuide I think I found an errata or missing text in R3-14/12 docs:

    5.7.1.2 Lock Sets
    All records, except for the conditions listed in the next paragraph, linked together directly or indirectly are placed in the same lock set. When dbScanLock is called the entire set, not just the specified record, is locked. This prevents two different tasks from simultaneously modifying records in the same lock set.

The thing is that this section ends here, there is no 'next paragraph'. Hope this helps.

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.