Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace Spectrum LSF
Created by Guest
Created on Jun 8, 2015

long-running daemons and cgroups

Vendor daemons are preventing us from implementing cgroups for process accounting.

We would like to implement cgroups for process accounting in our LSF
cluster to resolve a long standing issue of processes escaping from
LSF control.

We have several vendor daemons that start as part of a user job that
will either run forever or until some internal inactivity timeout. In some
cases, the daemons are shared among users. The first job will start
the daemon and subsequent jobs will use that process rather than starting
its own. The daemons run on a well known port, so only one can run at a time.

With cgroup accounting enabled, the job that started the daemon will
remain in a RUN state until the job is killed or the daemon reaches
its inactivity timeout. In some cases, it might not reach the timeout
because of other jobs keeping the process active.

One possible solution we are looking into is starting the shared daemons
at boot time from a non-LSF user account. That might solve one issue,
but we still have daemons that start for each user and don't appear to
timeout. I am talking to the vendor about the behavior to see if there is
anything we can do to ensure those daemons only last as long as the job.

If we are unable to resolve the issue with vendor changes or vendor
guidance, I've considered options such as a post-exec that would kill
the processes belonging to the job's cgroup. We can't blindly kill
everything in the cgroup because that would kill res or other LSF daemons
resulting in the jobs always exiting with an EXIT status rather than DONE.

Has anyone else faced this issue? Are there alternate solutions to the
problem or ideas on how to solve it? Could LSF be modified to exclude
certain processes from the cgroup?

  • Guest
    Jul 13, 2015

    This is a bit of a catch-22 problem. Cgroups is designed to track all processes at the kernel level which prevents users/apps from spawning of processes that are not managed or accounted for.
    A process can leave the cgroup by calling lsgrun to launch it - this will work even when LSF_DISABLE_LSRUN=Y is set, and will only work to the local host.

  • Guest
    Jun 9, 2015

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