IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Dec 16, 2014

RELATED IDEAS

LSF enforced limits

LSF currently inherits the environment (limits) from the system when the LSF Daemons are started, and doesn't compensate based on whether the LSF daemons are started by process 1 (init) or by root.
If LSF is configured to startup as part of the system boot process, the LSF daemons are started by the init process and changes that are configures in /etc/security/limits.conf, e.g. Max Locked Memory, are not applicable. However, if the LSF daemons are started on a system that is already running, the configured parameters in /etc/security/limits.conf are applicable.
The default "Max Locked Memory" on a RHEL 6.4 system is 64K.
If the system is configured to change the defaults "Max Locked Memory" to unlimited, LSF will behave differently depending on how LSF was started on the LSF Servers.

The request is for LSF to provide a mechanism where the limits enforced by LSF are consistent whether LSF is started by the init process or started by root.
Current work around is to customize /etc/init.d/lsf to change the hard and soft "Max Locked Memory" limit to match the setting in / etc/security/limits.conf. The work-around is challenging from a maintenance point of view, and in particular during system upgrades.

  • Guest
    Reply
    |     Mar 26, 2015

    Hi Bhavin,

    The feature USE_PAM_CREDS may resolve your concern.

    - When this feature is enabled, LSF will use the PAM API to set the limits defined in /etc/security/limits.conf.
    - One limitation is that the feature doesn't work for jobs launched from blaunch.
    - USE_PAM_CREDS is a queue and application profile parameter.
    - Documentation is found in the lsb.queues and lsb.applications sections of the configuration reference. The lsb.queues reference for LSF 9.1.3 can be viewed online at the URL: https://www-01.ibm.com/support/knowledgecenter/SSETD4_9.1.3/lsf_config_ref/lsb.queues.5.dita
    - The feature was added in LSF 7.0.3.
    - PAM must be configured before the feature will work. To configure PAM, create a file (/etc/pam.d/lsf) and add the following lines to the file.

    auth required pam_localuser.so
    account required pam_unix.so
    session required pam_limits.so

  • Guest
    Reply
    |     Jan 14, 2015

    This is not an LSF behaviour, but a standard linux kernel behaviour. No process started by init.d reads /etc/security/limit.conf. /etc/security/limits.conf is only read by pam interactive sessions.

    Blindly unlimited max locked memory may not be the desirable option in all clusters.

    We willl look at this in more detail in a future release.

  • Guest
    Reply
    |     Dec 18, 2014

    Creating a new RFE based on Community RFE #63519 in product Platform LSF.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.