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:
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
Do not place IBM confidential, company confidential, or personal information into any field.