Ralph Lange wrote:
> I'm using an absolute symbolic link, i.e. simple string replacement when
> processing the link would result in the correct path. (Still the problem
> might be due to the file system crossing.) And - I forgot to tell -
> reading a file works perfectly, just writing produces the error.
>
> Do you think this fits the FAQ explanation?
I don't. I wondered whether it might be that you're mounting a
filesystem called '/' and '/something', but if you get reads working
from the '/something' filesystem and you are sure these are through nfs
and not via rsh or ftp then that's unlikely.
What does nfsAuthUnixShow tell you about the uid/gid/gids of the target?
Are they actually set to who you think they are? If not, you might
expect that behaviour if it's allowed read-only access to the directory.
-- Andrew
___
.' `. Andrew Johnson, Head of Electronics
/ Royal ) Royal Greenwich Observatory
\ Greenwich Madingley Road, Cambridge, CB3 0EZ
| Observatory Tel: +44 1223 374823 Fax: 374700
+---------- WWW: http://www.ast.cam.ac.uk/~anj
- Replies:
- Re: NFS vxWorks Access Rights Ralph Lange
- References:
- Re: NFS vxWorks Access Rights Ralph Lange
- Navigate by Date:
- Prev:
Re: NFS vxWorks Access Rights Ralph Lange
- Next:
Re: NFS vxWorks Access Rights Ralph Lange
- 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
- Navigate by Thread:
- Prev:
Re: NFS vxWorks Access Rights Ralph Lange
- Next:
Re: NFS vxWorks Access Rights Ralph Lange
- 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
|