Hi Ake, (belated reply)
On Nov 3, 2016, at 11:29 AM, Åke Sandgren <[email protected]> wrote: >> 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) > > Not sure what you mean here, the current license file we have for 2017 > work with the old intel 11 compiler suite and everything inbetween… Don’t be too much sure about this. ;) I’ve seen Intel breaking intermediate impi licensing (selectively and intentionally). While all else was working. Yes, just entirely surprising. > You can just add the new license resources to the file the license > server is using... Yes, this helps plenty. However, then you still need to update your license files at client side, NOT only server side. From that follows, that having a central point of control is very beneficial/essential. I’m not writing the FlexLM codebase, nor do I know why Intel does all this. I’m just reporting the case. Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
