Re: [gridengine users] Different ulimit settings given by different compute nodes with the exactly same /etc/security/limits.conf

Hi, > Am 03.07.2019 um 04:39 schrieb Daniel Povey : > > Could it relate to when the daemons were started on those nodes? I'm not > sure exactly at what point those limits are applied, and how they are > inherited by child processes. Correct. The limits in place when sgeexecd is started are us

Re: [gridengine users] Different ulimit settings given by different compute nodes with the exactly same /etc/security/limits.conf

Could it relate to when the daemons were started on those nodes? I'm not sure exactly at what point those limits are applied, and how they are inherited by child processes. If you changed those files recently it might not have taken effect. On Tue, Jul 2, 2019 at 10:36 PM Derrick Lin wrote: >

[gridengine users] Different ulimit settings given by different compute nodes with the exactly same /etc/security/limits.conf

Hi guys, We have custom settings for user open files in /etc/security/limits.conf in all Compute Node. When checking if the configuration is effective with "ulimit -a" by SSH to each node, it reflects the correct settings. but when ran the same command through SGE (both qsub and qrsh), we found t