Opened 13 years ago
Last modified 10 years ago
#468 new enhancement
IZ2395: pam and/or max locked memory
Reported by: | sgaure | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | sge | Version: | 6.1u2 |
Severity: | Keywords: | Linux execution | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=2395]
Issue #: 2395 Platform: All Reporter: sgaure (sgaure) Component: gridengine OS: Linux Subcomponent: execution Version: 6.1u2 CC: None defined Status: NEW Priority: P4 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: pollinger (pollinger) QA Contact: pollinger URL: * Summary: pam and/or max locked memory Status whiteboard: Attachments: Issue 2395 blocks: Votes for issue 2395: 1 Opened: Wed Oct 10 13:19:00 -0700 2007 ------------------------ We have infiniband drivers which require the user to have a limit of max locked memory of at least 4MB, which is above what is default. To ensure that this is set high enough we have set it in /etc/security/limits.conf on the compute-nodes. This is sufficient for ssh-logins (i.e. qlogin), but it turns out that sge_shepherd does not check with pam when starting processes, instead it inherits its lock limit from sge_execd, which inherits it from /etc/rc, i.e. init. There is no h_memlock/s_memlock in the queue configurations. I suggest that either a h_memlock/s_memlock is added along with h_data/s_data and the other limits, and/or that the shepherd optionally checks limits and other things with pam via system-auth or some other config in /etc/pam.d.
Note: See
TracTickets for help on using
tickets.