[OpenAFS] OpenAFS 1.7.0600 does not seem to handle symbolic links correctly

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC4D6A35F305AFAF6DE40B99E
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Gary:

What is the target path of the symlink?

  symlink list <symlink>

Is that target path a relative symlink or an absolute symlink (begins
with '/')?

If it is an absolute symlink, does it begin with "/afs"?

Does the symlink contain a component with an embedded "@sys"?

If so, does there exist any of the "fs sysname" values in the parent
directory to match the @sys name expansion?

Jeffrey Altman

On 2/13/2012 10:16 AM, Gary Coryer wrote:
> I installed the latest update (as of thursday last week) for OpenAFS
> 1.7.0600 last week on my windows 7 afs client.  Everything runs fine
> until I get to a symbolic link in my Linux file system.  The Windows 7
> navigtor will not follow the symlink, it will not change directory from=

> the command line either.  The navigator seems to think it is a link
> because it has the chain symbol on the icon but the icon is faded.  I
> get a message when I try to follow the symlink that I do not have
> permission.  I have no trouble traversing the symlink on the linux
> client I use (don't believe Linux client is running open afs, I don't
> own that box, so that last was a statement that I do have file system
> permissions, not a difference in windows versus linux implementations).=

> This is a new install of the OpenAFS to update my laptop.  I can get to=

> all the files in the file system until I hit a symlink, so everything
> else runs really nice.  Another possible difference is that its more
> likely that access to file system objects that I symlink to is granted
> via a group permission, my own files inside the symlink perimeter are
> more likely to be accessed via my user id. =20
> Any ideas?
> Gary Coryer
>=20


--------------enigC4D6A35F305AFAF6DE40B99E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJPOnCnAAoJENxm1CNJffh4+2cH/R5xIZaxFdzlOFUYztt6OVJD
HPwcQIWtJit3YXGne+p0cd7K63glaso2xwZJh6m+XOaTYMwOwQb6kk5UVMRczGhK
mTNRK0QuKabHzGeV1uGBdOOUHiP7ZV5f9G4Yf3+lkp4xCDzADgFwO8EioH4tTSQI
/jtAzIS/6YbZy9uf0mG1TjGkH9JV3j/KRUZSp5Vc1v9hTTO2arv26PP5QtNyDkec
1yV8fmmwbyR4EpXkKr/udKrPtHENVY1iW1URmtdTJko6o6C53+KAUPAiTbQFCX0y
CppGmG1kC/ohCS0A5FoVDFUPHZ44ZnqFnx0wJwjyCsCE9n2iztga9oKz5U/LZ5I=
=wGht
-----END PGP SIGNATURE-----

--------------enigC4D6A35F305AFAF6DE40B99E--