1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Problem NFS mounting Centos 7 file systems from vxWorks 5.5 |
From: | Torsten Bögershausen <[email protected]> |
To: | Mark Rivers <[email protected]>, "[email protected]" <[email protected]> |
Date: | Thu, 19 Jan 2017 07:37:45 +0100 |
Is anyone running vxWorks 5.5 with a Centos 7/ RHEL 7, etc. modern NFS server?
Not me. But one observation I made is that Centos 7 uses NFS 4. To my understanding NFS 4 does not map the numerical user/group id"1:1", by default, but wants to translate the remote user id into a local one in some way.
And this is a security improvement. In short: We needed to tweak a file called /etc/idmapd.conf. I can dig out the details later. Can you mount Centos 7 -> Centos 7 ? On 19/01/17 02:00, Mark Rivers wrote:
Folks, We are mostly running VxWorks 6.9.4 now, and with that we have no problem NFS mounting file systems on Centos 7. However, we have a few IOCs that still need to run VxWorks 5.5. These can mount file systems on Centos 5 servers fine. However, on Centos 7 we see the following: - The NFS mount command from vxWorks succeeds with no error - showmount on the Centos 7 system shows that the vxWorks system has mounted the file system OK - However, the vxWorks system cannot actually read or write any files on the file system. If I type the “ls” command in a valid directory I get Cant’ open “null”. Value=-1 The problem is not file permissions, it works fine if we are running the identical IOC with vxWorks 6.9.4, and we have tried setting the files in that directory to mode 755. Is anyone running vxWorks 5.5 with a Centos 7/ RHEL 7, etc. modern NFS server? If so, how does one get it to work? Thanks, Mark