[vedranm@inf2 ~]$ man ls No manual entry for ls [vedranm@inf2 ~]$ echo $MANPATH /usr/share/man/mpich2 [vedranm@inf2 ~]$ rpm -qa | grep mpich2 mpich2-1.4.1p1-1.fc16.x86_64 mpich2-devel-1.4.1p1-1.fc16.x86_64
Jussi Lehtola, could you please help with this?
That's a good question, since MANPATH overrides the default configuration. Maybe MANPATH should be set so that it also includes the default man dir /usr/share/man. This is probably also an issue with openmpi et al.
Thanks for your response. From what I see on the other machine without mpich2 and openmpi, default configuration for $MANPATH is unset. Not sure if that's intended. On this machine I have in /etc: [vedranm@inf2 ~]$ find /etc | xargs grep MANPATH 2> /dev/null (...) /etc/modulefiles/openmpi-x86_64:prepend-path MANPATH /usr/share/man/openmpi-x86_64 /etc/modulefiles/mpich2-x86_64:# Define prefix so PATH and MANPATH can be updated. /etc/modulefiles/mpich2-x86_64:prepend-path MANPATH /usr/share/man/mpich2 /etc/bash_completion.d/man: manpath=$MANPATH Could it be a bash or environment-modules issue then?
from the man man page: MANPATH If $MANPATH is set, its value is used as the path to search for manual pages. By default nothing uses MANPATH, instead the configuration is (AFAIK) in /etc/man_db.conf. However, this approach is not usable for the environment modules approach. I don't know what would be the best approach: change the system-wide shell defaults to set MANPATH to the system directories (so that the MPI stuff would work without any changes), or modify each of the MPI packages and add the system man directory to the environment modules.
cc-ing to Orion, the maintainer of environment-modules Manpath issue v.s. environment-modules: bug 756951 bug 753760 (this) bug 753920
Yup, this is a modules issue. I've reported upstream. I've been unable to create a fix due to some internal changes in the code that I don't understand.
One of the quickest workarounds may be: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/2009-May/039520.html
environment-modules-3.2.9c-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/environment-modules-3.2.9c-1.fc16
environment-modules-3.2.9c-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/environment-modules-3.2.9c-1.fc15
Package environment-modules-3.2.9c-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing environment-modules-3.2.9c-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16561/environment-modules-3.2.9c-1.fc16 then log in and leave karma (feedback).
*** Bug 758486 has been marked as a duplicate of this bug. ***
(In reply to comment #10) > # su -c 'yum update --enablerepo=updates-testing environment-modules-3.2.9c-1.fc16' This update fixed the problem for me. Thanks!
environment-modules-3.2.9c-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
environment-modules-3.2.9c-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.