Here in SLAC, we faced the same problem but under Linux. We first ran the IOC with user1, generating autosave files with user1 as owner and next, we ran it with user2. The result was that on the second time, autosave tried to fchmod a file as user2, having user1 as the owner of the file, what is not allowed in Linux, and probably in your NFS server.
If you change the owner of your autosave files, probably you will not see the messages anymore.
Even having this solution, I see 2 improvement opportunities here:
1 - autosave is changing file permissions by default and does this silently. I think this should be an option to be chosen by the IOC engineer.
2 - autosave shows error -1 and this can be anything. There is no way to diagnose what is going on.
I am working on a patch with some suggestions to address this, and I will make a GitHub pull request soon.
I don't have experience with VxWorks, but maybe it can work for you, Greg. For now, if you want to build autosave without the need of changing file permissions, you can:
- modify asApp/src/Makefile, adding:
USR_CPPFLAGS += -DSET_FILE_PERMISSIONS=0
- modify asApp/src/save_restore.c, changing:
#define SET_FILE_PERMISSIONS 1
De: email@example.com <firstname.lastname@example.org> em nome de J. Lewis Muir <email@example.com>
Enviado: quarta-feira, 22 de março de 2017 11:13
Para: Lawson, Gregory S.
Assunto: Re: Vxworks nfs write error?
On 03/17, Lawson, Gregory S. wrote:
> Host is RHELWS kernel 2.6.32-642.
What version of RHEL is that?
What version of NFS is the server providing?
- Re: Vxworks nfs write error? Lawson, Gregory S.
- Vxworks nfs write error? Lawson, Gregory S.
- Re: Vxworks nfs write error? J. Lewis Muir
- Navigate by Date:
EPICS meeting in May 15-18 at KURRI (3rd announce) 上窪田＠KEKTokai
CSS Alarm Handler Status Messages Abdalla Ahmad
- Navigate by Thread:
Re: Vxworks nfs write error? J. Lewis Muir
Re: Vxworks nfs write error? Lawson, Gregory S.