Closed keenanlang closed 8 years ago
I think there is still a reason to have auto_positions.req and auto_settings.req. Users can modify these files to add whatever PVs they want that aren't in any database-associated .req files. Also, users who want to upgrade without switching to autosaveBuild (especially non-APS users) will have a less bumpy transition if we retain these files (for now?).
Created two separate iocsh files, one for autosaveBuild and one where you can specify a positions and a settings file to allow people who don't use autosaveBuild to take advantage of the scripts. Also moved all the autosave settings to their own script. XXX will end up looking like so:
iocshLoad("$(AUTOSAVE)/iocsh/autosave_settings.iocsh", "SAVE_PATH=$(STARTUP)")
iocshLoad("$(AUTOSAVE)/iocsh/autosaveBuild.iocsh")
iocshLoad("$(AUTOSAVE)/iocsh/save_restore.iocsh", "POSITIONS_FILE=auto_positions.req, SETTINGS_FILE=auto_settings.req")
And then the calls to set the request paths.
Added iocsh script that takes in a path to put save files and sets up the autobuild system, sets defaults for various autosave settings, and starts the necessary monitor processes. All the user needs to do is add the directories to search for req files.