[OpenAFS] =?UTF-8?Q?AW=3A_Re=3A_=5BOpenAFS=5D_Windows_client_Cygwin_and_symlinks_?= =?UTF-8?Q?on_afs_volume?=
Tue, 12 Apr 2011 16:01:46 +0200
> 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
> bash-3.2# pwd
> 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
Did you create the symlink within Cygwin? All my symlinks are created on AFS by a Linux client.
I experience this error for all symlinks.
Does it work for you when you use the "/cygdrive/DriveLetter" syntax? The "/afs/" syntax does not work for me in Cygwin environment (Windows Client 1.5.75 on XP).
Interestingly, I can inspect files within a symlinked directoroy when I know its name.
"This is the conten of test.txt"
> 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.
I will give it a try.