Experimental Physics and
| |||||||||||||||||
|
Hi Emmanuel,
For most of the databases I use, there is a corresponding autosave-request file, written by the author of the database. I think the author is probably the entity best placed to determine which PVs need to be autosaved so that the database can reinitialize itself to the state it was in before the ioc reboot. I would not trust dbgrep to choose autosave PVs. Normally, I just include a line of the form file <request file> <macro definitions> for each database whose PVs I want autosaved. With this practice, an ioc configuration doesn't have to specify PVs at all, so doesn't have to react to PV-name changes. By the way, there is code in synApps (makeAutosaveFiles.py) that will go through all of the .cmd and .substitution files in an ioc directory, find corresponding request files, if they exist, and write a request file for the ioc. This software relies on a naming convention: for each mydatabase.db there is a mydatabase_settings.req. Tim From: "Emmanuel Mayssat" <[email protected]>
| ||||||||||||||||
ANJ, 20 Apr 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |