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

["Webb, Brad via Tech-talk" <tech-talk at aps.anl.gov>]

Hi

> Can you say more about how your IOCs are being launched?
procServ --name myIOC --logstamp --logfile xxxvar/myIOC/log/myIOC.log --pidfile
xxxvar/myIOC/procServ.pid --chdir xxx/myIOC/iocBoot {port} ./st.cmd'

> Do multiple IOC processes share the same $PWD
No

On Fri, 2024-11-01 at 11:26 -0700, Michael Davidsaver wrote:
> On 11/1/24 06:09, Webb, Brad via Tech-talk wrote:
> > After upgrading to EPICS 7.0.8.1 I see the errors below in the IOC start-up console output.
> > ERROR Permission denied (13) writing '.iocsh_history'
> > ERROR Permission denied (13) writing '.iocsh_history'
> > 
> >  From the release notes:
> > https://urldefense.us/v3/__https://github.com/epics-base/epics-base/blob/7.0/documentation/RELEASE_NOTES.md*persist-history__;Iw!!G_uCfscf7eWS!fxC6WWyvShbxHs8jPNfGxcc-Yd3gb7wGySPtGjoGKon5HqQERrpNd3FD4NrQvKubT7JRig5xbohNUi8W3jbS$
> > 
> > I find this section about setting the environment variable:
> > Persist history
> > Attempt to read and write command to a file (./.iocsh_history by default). Name may be
> > overwritten
> > with by setting $EPICS_IOCSH_HISTFILE to an alternate path, or disabled by setting to an empty
> > string.
> > 
> > So, my question is how can this variable be set on a per IOC basis so that each IOC can have its
> > own
> > unique path for the history file?
> 
> Whatever mechanism you are using to launch IOC processes would
> need to compute and set $EPICS_IOCSH_HISTFILE .
> 
> Since you did RtM, I appreciate that this is not by itself a
> useful reply :)
> 
> Can you say more about how your IOCs are being launched?
> Do multiple IOC processes share the same $PWD and/or does
> an IOC not have permission to create files in $PWD ?
>