NFS4 wrong behavior with symbolic link

[Trond Myklebust]

On Mon, 2007-04-30 at 13:52 -0400, Charland, Denis wrote:
> 
> This bug is related to nfs-utils-1.0.7. It also occurs with version
> 1.0.12.
> 
> On the NFS4 server, I create the following script file
> /home1/publique/bin/test_script:
> 
> #!/bin/bash
> 
> echo "Hello world!!!"
> 
> exit
> 
> [denis at fn3 ~]$ ls -al /home1/publique/bin/test_script
> -rwxr-xr-x 1 publique mod 41 Apr 24
> 11:11 /home1/publique/bin/test_script
> 
> On the NFS4 client, /home1 is mounted and /usr/local is a symbolic
> link to
> /home1/publique.
> 
> [denis at ng64 ~]$ df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda2 20315844 8087488 11179716 42% /
> /dev/sda1 101089 12298 83572 13% /boot
> /dev/shm 1027616 0 1027616 0% /dev/shm
> fn3:/ 1437046488 876130104 487918636 65% /home1
> 
> 
> [denis at ng64 ~]$ ls -al /usr/local
> lrwxrwxrwx 1 root root 15 Apr 23 17:06 /usr/local -> /home1/publique
> 
> If I execute the script using the symbolic link:
> 
> [denis at ng64 ~]$ /usr/local/bin/test_script
> -bash: /usr/local/bin/test_script: /bin/bash: bad interpreter: Is a
> directory
> 
> Wrong behavior.
> 
> Now, if I execute the script a second time using the symbolic link:
> 
> [denis at ng64 ~]$ /usr/local/bin/test_script
> Hello world!!!
> 
> Right behavior. The script works everytime after.
> 
> If I unmount and remount /home1, I can reproduce the same behavior
> again.
> 
> I don't have this problem if I mount /home1 using NFS3. So, the
> problem is
> NFS4 related. 

'uname -a' and all that good stuff?

Trond