About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Having LSF create this logon file, without actually doing a logon, would have the knock on effect of triggering exceptions in security software that was looking for spoof logons.
On the avoid of the security focal, we will not be implementing this.
I heard that some user uses /run/user/$uid.
If interactive jobs make /run/user/$uid the same as other logins, it will help the user.
If it's not possible, I'll try to discuss to the user again.
We don't under what the specific use case is, or the value of doing this.
/run/user/$uid is created when a login is initiated. As support has stated, LSF does not perform a "login" when starting a job