On 4/12/2011 7:11 AM, Axel M wrote: > > We use (Linux) symlinks on our afs volume for some directories. The symlinks > are created by the Linux AFS client. > On Windows, Explorer does show this symlinks correctly as directories and 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 users). > 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.
signature.asc
Description: OpenPGP digital signature
