[OpenAFS] Problem with afs path names /afs/.bla.bla vs. /afs/bla.bla

Dr Yuri A Shitov y.shitov@imperial.ac.uk
Tue, 16 Feb 2010 11:58:35 +0000


Hi to all,

On majority of systems afs directory could be accessed by both paths:
/afs/.bla.bla/...
and
/afs/bla.bla/...

(difference in point  prefixing  a domain name). But I have found recently
the system where first path is not accessible:

[chitov@nemo4 SNSW]$ ls 
/afs/cern.ch/sw/lcg/external/clhep/1.9.2.3/slc4_ia32_gcc345/lib
libCLHEP-1.9.2.3.a             libCLHEP-Exceptions-1.9.2.3.so        
libCLHEP-HepPDT-1.9.2.3.so         libCLHEP-RefCount-1.9.2.3.so
...
[chitov@nemo4 SNSW]$ ls 
/afs/.cern.ch/sw/lcg/external/clhep/1.9.2.3/slc4_ia32_gcc345/lib
ls: /afs/.cern.ch/sw/lcg/external/clhep/1.9.2.3/slc4_ia32_gcc345/lib: No 
such file or directory

The problem is that config file used during compilation returns path 
with point:

[chitov@nemo4 SNSW]$ clhep-config --libs
-L/afs/.cern.ch/sw/lcg/external/clhep/1.9.2.3/slc4_ia32_gcc345/lib 
-lCLHEP-1.9.2.3

which is then can't be accessed and compilation fails.

I'm wondering what should be done on the system to allow both types of 
addressing of /afs  paths.
Please, cc-copy your answer to this mail

Thanks in advance,
Yuri