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
Dear all,
we have several applications unable to work properly when they are executed by launching Vnc jobs.
We receive several dbus and dconf error messages which can be traced back to the fact that the directory /run/user/$uid isn’t found.
This lead to a user environment not set and as a consequence the user variables used by applications are missing.
Usually, when user logon the host, /run/user/$uid is created by pam_systemd and used for storing files used by running processes for that user. When a user logs out, and no active sessions remain, pam_systemd will remove the /run/user/$uid directory.
As you stated in CASE TS017274952, LSF does not use "ssh" or "rsh" to start jobs. When a job runs on execution host, sbatchd and res do not call pam_systemd by default, so "/run/user/$uid" is not created.
Our requirement is to have the Linux PAM support in LSF to be able to set properly the user variables used by application launched via Vnc job.
Many thanks in advance for your support and collaboration
Kind regards
Needed By | Yesterday (Let's go already!) |
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.
Indeed, the results obtained by adding session optional pam_systemd.so to /etc/pam.d/lsf were not positive, as you stated.
Let me explain better the use case for which we need to set up the environment correctly: Vnc sessions are used as virtual desktops by users. There is a need for the user to login as if he using a 'traditional desktop', hence the need for the dbus configuration to be correctly valued.
Currently we are using a template that launches a script that does an SSH and then launches the Vnc session in which the application is executed.
When the LSF service starts a job on behalf the user it does not perform an OS login, so pam_login() is not called, and that pam_systemd is not invoked to /run/user/$uid is not created.
Changing LSF to perform a login() would fundamentally change an established architecture, and is not something we would do.
As previously discussed, you could add
session optional pam_systemd.so
to /etc/pam.d/lsf, but it may result in some other unexpected behaviour as login() has not been called, and not tty would be associated with the session, so may have other issues. Furthermore, you could not use LSF's own cgroup support at the same time.