2016-11-03 15:12 GMT+01:00 Vanzo, Davide <[email protected]>:
> Pablo, > > I am trying to install the 2017.1 version and I will be happy to share as > soon as I fix a little issue with the MKL. > thanks! > > -- > Davide Vanzo, PhD > Application Developer > Adjunct Assistant Professor of Chemical and Biomolecular Engineering > Advanced Computing Center for Research and Education (ACCRE) > Vanderbilt University - Hill Center 201 > (615)-875-9137 > www.accre.vanderbilt.edu > > On Nov 3 2016, at 6:23 am, Pablo Escobar Lopez < > [email protected]> wrote: > >> Hi Ole, >> >> Could you share your iomkl easyconfig using the latest intel2017 compiler? >> >> regards, >> Pablo. >> >> 2016-11-03 12:07 GMT+01:00 Fotis Georgatos <[email protected]>: >> >> Hi Ole, all, >> >> On Nov 2, 2016, at 2:33 PM, Ole Holm Nielsen <[email protected]> >> wrote: >> > On 11/02/2016 12:52 PM, Åke Sandgren wrote: >> >> env INTEL_LICENSE_FILE=port@host eb intel-2016a.eb ... >> > >> > Fantastic, this worked for me! I wonder where the usage of >> license_file and/or INTEL_LICENSE_FILE within EB might be documented? >> >> It SHOULD ;-) >> >> There’s one caveat with the port@host approach: >> >> One day, Intel’s practices will force you to setup a second license server >> (either because you need to setup a new flexlm server version or, >> because Intel has the nasty habit of silently deprecating old components >> in new licenses >> and you need to point to a test instance without touching your production >> instance yet) >> >> So, it’s more beneficial to point to a file, so that you can easily >> redirect clients >> to a new server instance, from a *single* point of control - without >> touching the modulefiles at all! >> If you have 100s of Intel modulefiles in module buildset trees, you know >> what I’m talking about! >> >> Also one more potential caveat: although it IS possible to drop in that >> one just the first 2 lines >> of the license file (ie. license server coordinates) don’t do that either >> and use the whole thing: >> I’ve met situations where certain Intel components (not all) have bugs >> and don’t cooperate well. >> I no longer have the Intel ticket numbers but you can take my word for >> it: I’ve spend endless hours around it. >> >> Last but not least, something I’ve not tried yet: you could be pointing >> instead to a licensefile >> sitting on /dev/shm, presumably populated at node boot time, so that you >> can have more granularity >> of control - at node level rather than cluster. This would permit you fi. >> to modify node behaviour >> in a rolling update fashion. I haven’t yet been hit by the absence of >> this but it’s a nice to have. >> >> Fotis >> >> -- >> echo "sysadmin know better bash than english" | sed s/min/mins/ \ >> | sed 's/better bash/bash better/' # signal detected in a CERN forum >> >> >> >> >> >> >> >> >> >> >> -- >> Pablo Escobar López >> HPC systems engineer >> sciCORE, University of Basel >> SIB Swiss Institute of Bioinformatics >> http://scicore.unibas.ch >> > -- Pablo Escobar López HPC systems engineer sciCORE, University of Basel SIB Swiss Institute of Bioinformatics http://scicore.unibas.ch
