I have sometimes wondered about trying to establish a conventional FS
location for IOC volatile data. Firstly for autosave. Something
analogous to what systemd's "StateDirectory=" tries to accomplish.
I strongly agree. Actually, I thought that was best (and common) practice for a long time.
IOCs clearly need two locations:
One - read-only - that contains their configuration.
One - read-write - for all their state: dbl/dbior/dbhcr output, autosave data, console log files, ... (would go under /var on local Linux)
With diskless IOCs, I remember having two separate NFS mounts for these two areas.
Cheers,
~Ralph
