<END>?" or "<END>??", where
"?" is any character. This allows dos files, which end with
"\r\n", to be restored.
# The normal save_restore directory setup, in st.cmd:
save_restoreSet_NFSHost("oxygen", "164.54.52.4")
set_savefile_path(startup, "autosave")
...
iocBoot()
...
(end of st.cmd)
...
# Type the following into the ioc's console
save_restoreSet_NFSHost("wheaties", "164.54.53.101")
# You'll get an immediate error if the old save file path doesn't
# exist, or has adverse permissions, on the new server.
set_savefile_path("/local/autosave", "")
# save_restore will immediately attempt to mount the new file path
The above code assumes the ioc has permission to mount file systems on the host ('wheaties', in this case) and that the ioc has read/write/execute permission to the directory in which it is supposed to write .sav files (in this case, '/local/autosave'). Neither of these conditions are likely to be met by default; you must take action to arrange them.
Save_restore cannot defend against adverse file permissions, or against the save directory (NFS mount point) disappearing altogether.
| OLD | NEW |
|---|---|
| sr_save_incomplete_sets_ok | save_restoreIncompleteSetsOk |
| sr_restore_incomplete_sets_ok | save_restoreIncompleteSetsOk |
| --no comparable function-- | save_restoreSet_IncompleteSetsOk(value) |
| reboot_restoreDebug | save_restoreDebug |
| --no comparable function-- | save_restoreSet_Debug(value) |
| reboot_restoreDatedBu | save_restoreDatedBackupFiles |
| --no comparable function-- | save_restoreSet_DatedBackupFiles(value) |
| --no comparable variable-- | save_restoreNumSeqFiles |
| --no comparable function-- | save_restoreSet_NumSeqFiles(value) |
| --no comparable variable-- | save_restoreSeqPeriodInSeconds |
| --no comparable function-- | save_restoreSet_SeqPeriodInSeconds(value) |
| NOTE: if save_restoreNumSeqFiles > 0, redundant .sav file will be written every save_restoreSeqPeriodInSeconds seconds | |
| --no comparable function-- | dbrestoreShow() |
| fdblist() | save_restoreShow(verbose) |
| NOTE: save_restoreShow() calls dbrestoreShow() | |
| save_restore_test_fopen | --no comparable variable-- |
| NOTE: test is no longer done | |
| create_periodic_set(file,period) | create_periodic_set(file,period,macro) |
| create_triggered_set(file,trigPV) | create_triggered_set(file,trigPV,macro) |
| create_monitor_set(file,period) | create_monitor_set(file,period,macro) |
| create_manual_set(file) | create_manual_set(file,macro) |
| reload_periodic_set(file,period) | reload_periodic_set(file,period,macro) |
| reload_triggered_set(file,trigPV) | reload_triggered_set(file,trigPV,macro) |
| reload_monitor_set(file,period) | reload_monitor_set(file,period,macro) |
| reload_manual_set(file) | reload_manual_set(file,macro) |
| NOTE: macro string is optional and supplements any macro strings defined in request files. You can only reload one set at a time; you must wait for a reload to complete before starting another one. | |
| NOTE: IN VERSIONS EARLIER THAN 2.7, Time PERIODS WERE SPECIFIED USING FLOATING POINT NUMBERS. THEY ARE NOW SPECIFIED AS INTEGERS (IN SECONDS). | |
| set_savefile_path(path) | set_savefile_path(path,pathsub) |
| set_requestfile_path(path) -> set_requestfile_path(path,pathsub) | |
| NOTE: if pathsub is specified, it is appended to path. The purpose of this change was to make it easier to use variabled defined in cdCommands as path elements. Example: set_requestfile_path(std,"stdApp/Db") | |
| --no comparable function-- | save_restoreSet_status_prefix(value) |
| NOTE: save_restore expects PV's with which it can display its status. Status PV's are request-file specific; the supplied database contains PV's for auto_positions.req and auto_settings.req only. If you use other request files, you can add your own PV's. It's OK if the PV's don't exist, but you will get informational messages when their absence is noticed. | |
| --no comparable function-- | save_restoreSet_NFSHost(host,IPaddress) |
| --no comparable variable-- | save_restoreRemountThreshold |
| NOTE: If save_restore is managing its own NFS mount (i.e., if calls to save_restoreSet_NFSHost() and set_savefile_path() succeeded) it will dismount and remount after save_restoreRemountThreshold consecutive I/O errors (e.g. to fix a stale file handle). | |
| ATTENTION |
|---|
This version is incompatible in one important respect with versions of
save_restore.c numbered lower than 2.6: The functions
|