Re: Weird file access problem with vxWorks

[Steven Hartman <hartman@fel.duke.edu>]

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
hartman@fel.duke.edu | 919-660-2650
Duke Free Electron Laser Laboratory