Hi Riccardo, On 09/05/16 13:28, Riccardo Murri wrote:
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.
It actually *does* fulfill the purpose, because the assumption is that the temporary directory is the same path across systems where Intel installations are being performed, and that $HOME is a shared filesystem.
So, it'll link $HOME/intel to /local/tmp/path/$USER/easybuild_intel (with your tmpdir setup).
I do admit this is not perfect though, since this approach will fail when you're running multiple Intel installations on the same system at the same time. Although, then again, this is not supported by the Intel installers anyway (one installer will detect the other, and blatantly abort).
- Given the symlink stuff above, I am even more convinced that a failure to clean up the tree should *not* be fatal.
Well, ok, maybe it shouldn't be fatal, but the only reason it's fatal now is that we like to clean up after ourselves, and not leave cruft behind left & right...
- 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 ...
My main question is why the intelremotemond stays behin; it doesn't happen for us... I guess this is related to it being started from an NFS directory (some kind of locking problem, maybe)?
In any case: using an NFS-mounted directory as tmpdir is not wise, it's likely it'll get you into trouble in other places too...
regards, Kenneth
