EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  <19971998  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  <19971998  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: NFS vxWorks Access Rights
From: [email protected] (Ralph Lange)
To: [email protected] (EPICS Tech-Talk)
Date: Mon, 21 Jul 1997 15:01:22 +0200 (METDST)
> Another NFS@vxWorks question:
> 
> [... long blurp about NFS problems - write access through links ...]
> 
> 	Has anyone any explanation for this? (I suppose this is a bug in
> the vxWorks nfsLib...)

I filed a problem report with WRS customer support Europe and they
answered:

[ Our nfs client has problems with links - this is an old story. I remember
[ the correct setting of the soft link's permission bits being part of it.
[ ... ]
[ But I just stumbled over SPR#6468 , sounds like your  problem . 

----------------------------------------------------------------------------

TITLE: 5.3.FCS-spr6468_nfs-symbolic-link.README

title: Symbolic linked file fails over NFS when opened for write mode.

AUTHOR: Rajesh

                         SCOPE                   DISCOVERED ON
              HOST:  All                        HP 9000/700
                     -------------------     -------------------
      ARCHITECTURE:  All                        68040
                     -------------------     -------------------
               BSP:  All                        mv162
                     -------------------     -------------------
PRODUCT / REVISION:  5.2, 5.3                   Tornado 1.0 FCS
                     -------------------     -------------------

DESCRIPTION OF PROBLEM: fopen() cannot open the file for writing if it
is a symbolic link to another file.
The following error is displayed  -

-> myfd = fopen ("/red1/rajesh/zoo","w")
myfd = 0x3b0f84: value = 0 = 0x0
-> printErrno
0xd = S_errno_EACCES
value = 0 = 0x0

RESEARCH: fopen works fine if the file is accessed over RSH instead of NFS
          or if you are in the same directory in which the symbolic file is
          present.

SPR / PATCH : 6468, Patch in nfsLib.c

FIX : 

<           return (FOLLOW_LINK);
---
>           return (OK);
726c726
<     where.name = fileName;
---
>     where.name = fullFileName;

-----------------------------------------------------------------------------

So this *was* a bug in the nfsLib...

Ralph

References:
NFS vxWorks Access Rights Ralph Lange

Navigate by Date:
Prev: Re: NFS vxWorks UMASK Ralph Lange
Next: DM dropping characters in text-entry? Steve Wampler
Index: 1994  1995  1996  <19971998  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: NFS vxWorks Access Rights Ralph Lange
Next: Re: NFS vxWorks Access Rights Tim Mooney
Index: 1994  1995  1996  <19971998  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·