About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
This RFE was delivered with the LSF 9.1.3.3 Fix Pack.
Fix Central URL:
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=Platform%2BComputing&product=ibm/Other+software/Platform+LSF&release=All&platform=All&function=fixId&fixids=lsf-9.1.3.3-spk-2015-Jun-build346694&includeSupersedes=0
Fix ID: lsf-9.1.3.3-spk-2015-Jun-build346694
Having it built in LSF will definitely help. Relying on LD_PRELOAD'ing a shared library at LSF startup is inconvenient at the least, for varous reasons like:
* external dependency
* unclear/undefined what will happen with child processes and LSF jobs
* harder to maintain
We will look at enabling this.
Keepalive is a socket option which must be enabled by the program. The kernel must support it, but it can *only* be enabled from within the program which opens the socket.
As a dirty hack, libkeepalive (http://libkeepalive.sourceforge.net/) could be used. However, I cannot see what side effects this has.
Is TCP keepalive enabled in the kernel on both masters? If so, the kernel should handle this automatically.
Creating a new RFE based on Community RFE #63295 in product Platform LSF.