Experimental Physics and
Industrial Control System

 
> Depending on what version of autosave you are using, you can work without any standalone autosave config files.
> Instead, you add annotations to your database records:
>
> record(type, "$(S):SomeRecord")
> {
> info(autosaveFields, "VAL LOW")
> In your IOC startup file you then add a command that auto-creates the request files from those database annotations:
>
> makeAutosaveFileFromDbInfo("autocreated.req", "autosaveFields");
> create_monitor_set("autocreated.req.req", 5)
>

Again, I want the flexibility to have 1 master IOC with 20 devices to be broken in several

(i.e. let's say I reconfigure the master IOC with 15 devices and 5 single-device IOCs that actively being developed)

This should of course be transparent from the EPICS client perspective

(i.e. restored values are the same)

[...]

I understand how to generate the req file (dbgrep * > file.req or more complicated as described above)

But what about restoring the PVs, i.e. what about the sav files? 

There are 2 solutions:

2/ Have one req file per device -->  one sav file used for all IOCs

But 

1/ Limits on number of sav files in autosave

2/ I anticipate issues as several processes try to write to the same file

Can this limit be raise to say ... 1000? 

Better yet, can this limit be removed?

I moved away from autosave some time ago due to that limit.

Is there anything that has the same functionality as autosave but would better fit my development methodology?

Regards,

--

Emmanuel