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

Reuti reuti at staff.uni-marburg.de
Wed Jul 3 06:14:09 UTC 2019


Hi,

> Am 03.07.2019 um 04:39 schrieb Daniel Povey <dpovey at gmail.com>:
> 
> 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 used (i.e. the one of the root user).


>  If you changed those files recently it might not have taken effect.
> 
> On Tue, Jul 2, 2019 at 10:36 PM Derrick Lin <klin938 at gmail.com> wrote:
> 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 that some Compute Nodes do not reflects the correct settings but the rest are fine.

Several ulimits can be set in the queue configuration, and can so different for each queue or exechost.

-- Reuti


> I am wondering if this is SGE related? And idea is welcomed.
> 
> Cheers,
> Derrick
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users




More information about the users mailing list