[Gap4] not showing up folders with NFS drive

2005-11-21
2013-04-18
  • My problem is: 

    When i try to browse on my Redhat Linux AS, Xeon 64 bit quad cpu, it's working fine until i get through a NFS mounted drive with a SUN Solaris OS. I can't see the folder structure or any . or .. folder name. I know it is not a security problem or access problem.

    Do you have an idea about that ?

    Thanks for your help.

    JD

     
    • James Bonfield
      James Bonfield
      2005-11-28

      This is most obscure. The filebrowser is largely just the Tcl/Tk one and I cannot see why it should not be able to list any files mounted on an NFS drive.

      Do programs like "ls" list the contents of the drive fine? My expectation would be that if it works at the unix prompt then it should also work within the program. Maybe if I was forced to clutch at straws I could say it's some strange symbolic link issue and a failure to identify a link to a directory as a directory, but I've never heard of this before.

      James

       
    • Hi,

      It's working fine with "ls" like command.  I have succefully compiled the source code and my problem was gone.  I'll try something else and let you know.

      Thanks for your help.

       
    • James Bonfield
      James Bonfield
      2005-12-09

      I'm still baffled as to the cause of this. All I can assume is that it was related to some linking error as recompiling it made the problem go away. Are there differences reported with ldd on my binaries vs your new compiled ones?

      James

       
    • LDD on my compiled version:
      ___
      libtk_utils.so => not found
              libtk8.4.so => /usr/lib64/libtk8.4.so (0x0000003cd6700000)
              libtcl8.4.so => /usr/lib64/libtcl8.4.so (0x0000003cd6300000)
              libm.so.6 => /lib64/tls/libm.so.6 (0x0000003cd5f00000)
              libX11.so.6 => /usr/X11R6/lib64/libX11.so.6 (0x0000003cd6100000)
              libdl.so.2 => /lib64/libdl.so.2 (0x0000003cd5d00000)
              libc.so.6 => /lib64/tls/libc.so.6 (0x0000003cd5a00000)
              /lib64/ld-linux-x86-64.so.2 (0x0000003cd5800000)

      LDD on your compiled version:
      ___

      linux-gate.so.1 =>  (0xffffe000)
              libtk_utils.so => /usr/local/staden/lib/linux-binaries/libtk_utils.so (0xf7fbd000)
              libtk8.4.so => /usr/local/staden/lib/linux-binaries/libtk8.4.so (0xf7efd000)
              libtcl8.4.so => /usr/local/staden/lib/linux-binaries/libtcl8.4.so (0xf7e64000)
              libm.so.6 => /lib/tls/libm.so.6 (0x00ac9000)
              libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00b7d000)
              libdl.so.2 => /lib/libdl.so.2 (0x00ac3000)
              libc.so.6 => /lib/tls/libc.so.6 (0x00997000)
              libread.so => /usr/local/staden/lib/linux-binaries/libread.so (0xf7dd8000)
              libmisc.so => /usr/local/staden/lib/linux-binaries/libmisc.so (0xf7dce000)
              libpng12.so.0 => /usr/local/staden/lib/linux-binaries/libpng12.so.0 (0xf7da5000)
              /lib/ld-linux.so.2 (0x0097e000)

      ____________-

      JD

       
    • Correction to my last post:

      here is the result for my compiled version again
      _______
      libtk_utils.so => /usr/local/staden/lib/linux-binaries/libtk_utils.so (0x0000002a95557000)
              libtk8.4.so => /usr/local/staden/lib/linux-binaries/libtk8.4.so (0x0000002a956af000)
              libtcl8.4.so => /usr/local/staden/lib/linux-binaries/libtcl8.4.so (0x0000002a958a4000)
              libm.so.6 => /lib64/tls/libm.so.6 (0x0000003cd5f00000)
              libX11.so.6 => /usr/X11R6/lib64/libX11.so.6 (0x0000003cd6100000)
              libdl.so.2 => /lib64/libdl.so.2 (0x0000003cd5d00000)
              libc.so.6 => /lib64/tls/libc.so.6 (0x0000003cd5a00000)
              libread.so => /usr/local/staden/lib/linux-binaries/libread.so (0x0000002a95a82000)
              libmisc.so => /usr/local/staden/lib/linux-binaries/libmisc.so (0x0000002a95c00000)
              libpng12.so.0 => /usr/local/staden/lib/linux-binaries/libpng12.so.0 (0x0000002a95d0d000)
              /lib64/ld-linux-x86-64.so.2 (0x0000003cd5800000)

       
    • James Bonfield
      James Bonfield
      2006-01-03

      Sounds like it's maybe some 64bit issue, albeit a bizarre one. Thanks for clarifying this some more.

      I've had several requests for binaries natively built with the AMD 64-bit extensions. I've no idea whether the Xeons are now sufficiently compatible with AMD that it'd work properly - I don't wish to support every derivative.

      James