Re: IOC Shell Persist history: ERROR Permission denied (13) writing '.iocsh_history'

[Ralph Lange via Tech-talk <tech-talk@aps.anl.gov>]

On Fri, 1 Nov 2024 at 22:49, Michael Davidsaver via Tech-talk <tech-talk@aps.anl.gov> wrote:

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