Experimental Physics and
Industrial Control System

On Wed, 29 Aug 2001, Mark Rivers wrote:
> Is this a problem with vxWorks, Linux or both?

It appears to be a problem with vxWorks. (Confirmed also with a Solaris 7
NFS server, VxWorks 5.4 client).

Looking at the snoop output of the process from the Solaris NFS server,
the VxWorks client never even does a Proc = 12 (Remove file). The Proc = 4
(Look up file name) and Proc = 5 (Read from symbolic link) both return OK
from the server, however.

My guess as to the source of this discrepancy is that vxWorks doesn't have
an understanding of sym links. For instance, on a Sun . . .

[67] hartman@rollins% mkdir /tmp/foo
[68] hartman@rollins% ln -s /tmp/foo /tmp/bar
[69] hartman@rollins% cd /tmp/bar
[70] hartman@rollins% pwd
/tmp/foo

Doing the equivalent in vxWorks would show pwd as /tmp/bar.

-- 
Steve Hartman
[email protected] | 919-660-2650
Duke Free Electron Laser Laboratory

References:

Weird file access problem with vxWorks Mark Rivers

Navigate by Date:

Prev: Re: Weird file access problem with vxWorks Brian McAllister

Next: Re: alarm handler confusion (and solution) Janet Anderson

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: Weird file access problem with vxWorks Brian McAllister

Next: A gmake problem in R3.13.4 J. Frederick Bartlett ([email protected])

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