Hello,
regarding this problem with `intelremotemond` keeping files open which
prevents whole-tree cleanup of the temporary directory on NFS:
- The issue is NFS-only: installation works fine on a local filesystem.
So the easiest workaround is to use the `--tmpdir=/local/tmp/path`
option.
- The EasyBlock in `intelbase.py` is using this temporary directory tree
as a "redirect" for stuff that the Intel installer would put into
`$HOME/intel`. While I appreciate the effort to keep the home
directory clean, it does not AFAICT fulfill its stated purpose
("enable parallel builds"): there can only be one symlink at a time so
you cannot install two different intel toolchains at the same time.
- Given the symlink stuff above, I am even more convinced that a failure
to clean up the tree should *not* be fatal.
- If anyone is curious about what the `intelremotemond` does, it is part
of a framework for collecting usage data and sending it to Intel:
https://software.intel.com/de-de/forums/intel-c-compiler/topic/506959
- The `intelremotemond` cannot be easily disabled during the
installation process, as it is embedded in a gzip'ed tarball within
the Intel Parallel Composer XE tarball ...
Ciao,
R
--
Riccardo Murri
http://www.s3it.uzh.ch/about/team/#Riccardo.Murri
S3IT: Services and Support for Science IT
University of Zurich
Winterthurerstrasse 190, CH-8057 Zürich (Switzerland)
Tel: +41 44 635 4208
Fax: +41 44 635 6888
