Sys Admin question

[boxyzzy]

OS: Red Hat Enterprise Linux Server release 5.2

Compiler: Intel FORTRAN 10.0.023

When a user compiles a particular FORTRAN program, the following messages appear in /var/log/messages. These messages do not appear for all compiles.

automount[3068]: lookup_mount: lookup(file): key "man" not found in map
automount[3068]: lookup_mount: lookup(file): key "man1" not found in map
automount[3068]: lookup_mount: lookup(file): key "man8" not found in map

These messages from automount indicate that /usr/share/man, /usr/share/man1, and /usr/share/man8 need to be exported and defined to automount.

This seem a bit odd / unnecessary / ridiculous. Am I missing something?

Thanks, in advance, for your help,

Mike

[joseph-krahn]

I had some odd behavior that stemmed from the fact that ifort calls "gcc --print-libgcc-file-name" to get information on linking with Linux system libraries. The system also had 'ccache' installed, which works by wrapping gcc to reduce compile time, mainly for badly designed Makefiles. It turned out that some ccache files in my home directory were corrupted. So, it is possible that the real culprit is some other auxliliary executable.

Also, is this just from compiling, or is the user running 'make'? Could it really be the Makefile causing this?

[boxyzzy]

This is from compiling. No Makefile is involved. -Mike

[Steven_L_Intel1]

I have never heard of this symptom before. Does this program have any INCLUDE statements? If so, do the filenames given in the INCLUDEs have paths that might trigger NFS automounts?

[joseph-krahn]

Here is a possibility: Does the user accidentally have a path environment variable set to include those MANPATH directories by mistake? It could be in PATH, LD_LIBRARY_PATH or FPATH, for example. If you can't find it, run "strace -f -o trace.log ifort ...", then check that trace log to see what is happening when that NFS path is accessed.