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,
Post an idea
Upvote ideas that matter most to you
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
See this idea on ideas.ibm.com
In our own pam module we use the function lsb_openjobinfo to identify if a user has a running job on the node or not. We do this to decide if the user can establish a connection to the node (usually the ssh connection at the beginning of a job). Unfortunately, the function lsb_openjobinfo talk to the fork of the mbatchd. So the information about the status of a job and the allocated slots could be 10s old (MBD_REFRESH_TIME ). This causes randomly errors before rewriting the pam module (see support case ID). All workarounds are not realy satisfying (check the status over 10s -> delay in runing the task, use a fake lsf.conf -> inconstency of configuration files or try to handle it by hostslist in a file -> additional I/O). So it would be greateful if one can directly talk to the mbatch daemon from the programming interface or have a parameter like NEWJOB_REFRESH to send updates to the fork of mbatchd of the event PEND to RUN.
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.
Salbem,
Have you reviewed the following pam module: https://github.com/IBMSpectrumComputing/lsf-plugins/tree/master/pam_lsf. It is designed to block logins with the exception of users who have jobs. It introduces a delay due to the fact that NEWJOB_REFRESH does not update the status information to 'RUN' from 'PEND' and populate the execution node. This is also important for jobs that are using 'bsub -IX' for SSH port forwarding.
I do agree with you that having a switch in the code for when you are asking for a specific host/user that we should be able to query the master batch daemon directly though.