Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: RE: autosave limitation?
From: Emmanuel Mayssat <emayssat@outlook.com>
To: "Kasemir, Kay" <kasemirk@ornl.gov>
Cc: "emmanuel_mayssat@lynceantech.com" <emmanuel_mayssat@lynceantech.com>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Tue, 16 Apr 2013 15:03:12 -0700
 
> 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:
1/ Have one req file per device  --> one sav file per device
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

is there a reason why autosave is limited to 8 files?
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




Replies:
Re: autosave limitation? Tim Mooney
References:
autosave limitation? Emmanuel Mayssat
Re: autosave limitation? Kasemir, Kay

Navigate by Date:
Prev: Re: EPICS UTC Time conversion Eric Norum
Next: RE: EPICS UTC Time conversion Kim, Kukhee
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: autosave limitation? Kasemir, Kay
Next: Re: autosave limitation? Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·