[OpenAFS] Windows client Cygwin and symlinks on afs volume

Jeffrey Altman jaltman@secure-endpoints.com
Tue, 12 Apr 2011 08:54:00 -0400


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

On 4/12/2011 7:11 AM, Axel M wrote:
>=20
> We use (Linux) symlinks on our afs volume for some directories. The sym=
links
> are created by the Linux AFS client.
> On Windows, Explorer does show this symlinks correctly as directories a=
nd it
> is possible to dive into these directories (I am aware of the delete
> problem, that's why the directories are only writable for a special use=
rs).
> However, Cygwin's bash has problems with these symlinked directories.
> When I do ls on such a symlink (AFS is mapped to drive Z)
> ls /cygdrive/z/WorkSpaces/linked_dir
> I get the error message "linked_dir is not a valid directory"

The AFS cache manager does not expose the existence of symlinks to
Windows.  Whatever failure your bash instance is experiencing, it has
nothing to do with symlinks.

/afs/athena.mit.edu/user/j/a/jaltman/sysinternals is a symlink to
"SysInternals".

bash-3.2#  pwd
//afs/athena.mit.edu/user/j/a/jaltman

bash-3.2# ls -lt
total 130
drwxr-xr-x 18 jaltman root  2048 2010-12-06 18:49 OldFiles
drwxr-xr-x  1 jaltman root 98304 2010-10-25 17:40 Private
drwxr-xr-x 21 jaltman root  6144 2010-10-02 18:11 Public
drwxr-xr-x  2 jaltman root  6144 2010-09-09 14:06 SysInternals
drwxr-xr-x  2 jaltman root  6144 2010-09-09 14:06 sysinternals

bash-3.2# ls sysinternals
ADExplorer.exe  Desktops.exe   LogonSessions.exe    SIEExtPub.zip
       accvio.EXE          ico00001.ico   procexp64.exe     regjump.exe
        strings.exe
ADInsight.chm   Disk2vhd.chm   Newsid.exe.manifest  Sid.mdp
       adplus_scripts.zip  ico207.ico     procmon.101.exe   resource.h
        sync.exe

What I suggest you do is use the SysInternals Process Monitor tool to
monitor the requests from bash.exe and see what exactly is failing.



--------------enigFE2C2D3AD3F9267016C83517
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)

iQEcBAEBAgAGBQJNpEtqAAoJENxm1CNJffh4cvkH/1soDBxSXMpK+K3niLSiNsXv
KlDYVIAyK2pzkWq995wxgLrnSW0TPS8/Jgf0kaF/42ubk2KXtvs8Ux9/rJMUxDsD
mg6BqgUzN1reSKpePvK2RwYglHEOfuOoWAsv0o526j9JKdEUj670Elf3dZ7nKwFa
KdZieaj9CjqLIXugzbaYRpBxgNTpHdzS+F0wGdUWbnrcr3dBOqeC17E/wnD9PwIL
0EV/7e9rNBFSLH6VrNyr5KaOGkixhoBTsS8Z9MVTNfKmye4dBbn1KEvgJcx8/+rY
VwpEC+Av2xdjWMpF/lWg1+3DkZVTIf68cMlgIViUL0+GkXV4PQ16Bl2LK+Gmu1c=
=eOnM
-----END PGP SIGNATURE-----

--------------enigFE2C2D3AD3F9267016C83517--