RE: autosave: makeAutosaveFiles()

["Zelazny, Michael Stanley" <zelazny@slac.stanford.edu>]

I cd to the directory before making the files:

[snip]
## Start saving datasets
cd("${IOC_DATA}/${IOC}/autosave-req")
epicsThreadSleep(1)
makeAutosaveFiles()
epicsThreadSleep(1)
create_monitor_set("info_settings.req",60,"")
epicsThreadSleep(1)
create_monitor_set("info_positions.req",60,"")
epicsThreadSleep(1)
[snip]

IIRC the sleeps make a difference, but I forget why at the moment.  Maybe lore from long ago.

________________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] On Behalf Of Wesley Moore [wmoore@jlab.org]
Sent: Thursday, August 02, 2012 8:18 AM
To: EPICS tech-talk
Subject: autosave: makeAutosaveFiles()

Techies,
    makeAutosaveFiles() dumps everything into the IOC's directory by default and I'd rather not clutter it up.  So I call makeAutosaveFileFromDbInfo() directly as a work-around.  Is this how others handle this or am I missing another trick?  Could this be a nice thing to easily add to autosave?  Something like makeAutosaveFiles("newdir/path")...

Here's what I've come up with as my work-around:

#
# from st.cmd...
#
#makeAutosaveFiles()
makeAutosaveFileFromDbInfo("autosave/req/info_settings.req", "autosaveFields");
makeAutosaveFileFromDbInfo("autosave/req/info_positions.req", "autosaveFields_pass0");
create_monitor_set("info_positions.req",30)
create_monitor_set("info_settings.req",30)

It works fine.  Just more curious about what you guys do.

Wesley