Hi Pablo,
That's actually something for Lmod to worry about.
man considers the default location for manpages if there's an empty
entry in $MANPATH, for example ":/scicore/soft/apps/GCC/4.8.4/share/man".
It's Lmod's job to make sure the empty entry stays there...
See also https://github.com/TACC/Lmod/issues/191
regards,
Kenneth
On 07/09/2017 12:05, Pablo Escobar Lopez wrote:
Hi,
I have noticed that when I load a module defining MANPATH in my
centos7 cluster then the default man pages are no longer available. E.g.
$> ml purge
$> man ls
This works fine and MANPATH is not defined
$> ml purge
$> ml GCC/4.8.4
$> man ls
No manual entry for ls
$> echo $MANPATH
/scicore/soft/apps/GCC/4.8.4/share/man:/scicore/soft/apps/binutils/2.25.1/share/man
I can workaround it doing this:
$> ml purge
$> export MANPATH=/usr/share/man
$> ml GCC/4.8.4
$> man ls
This works fine
$> echo $MANPATH
/scicore/soft/apps/GCC/4.8.4/share/man:/scicore/soft/apps/binutils/2.25.1/share/man:/usr/share/man
Before I was not hitting this problem because I had a file
/etc/profile.d/sge.sh which defines MANPATH on login but now that I no
longer define MANPATH on login I noticed this problem.
Did anyone else experience this problem? I can workaround it by
adding a profile file /etc/profile.d/man.sh which defines
"MANPATH=/usr/share/man" on login but before doing it I wanted to ask
in case someone suggest a different/better approach.
Maybe EasyBuild should make sure that MANPATH always contains
/usr/share/man ?
Pablo.
--
Pablo Escobar López
HPC systems engineer
sciCORE, University of Basel
SIB Swiss Institute of Bioinformatics
http://scicore.unibas.ch
