[GE users] /etc/security/limits.conf

Hristo Iliev hristo at phys.uni-sofia.bg
Tue Jun 26 08:31:46 BST 2007


Hi, Andy,

Debian based distros have recently swiched to upstart that replaced SysV 
init and thus are not aware of /etc/initscript. Not sure for recent RedHat
derviatives.

Hristo

On Mon, 25 Jun 2007, Andy Schwierskott wrote:

> Hi,
>
> on Linux the file
>
>  /etc/initscript
>
> should do the job for setting limits and defaults.
>
> See initscript(5) for more information.
>
> I'm note sure if all init(1) processes on all Linux distributions adhere to
> this convention.
>
> Andy
>
>> Hi Andy,
>> 
>> Andy Schwierskott schrieb:
>>> Hi,
>>> 
>>> running jobs are not affected when the execd is shutwond and restarted.
>>> The proper suggest way would be:
>>>
>>>    - disable the queue instances an the affected host
>>>    - shutdown execd('s)
>>>    - make the change to /etc/init.d/sgeexecd but for safety reasons to
>>>      <sge-root>/<cell>/common/sgeexecd as well
>>>    - restart execd('s)
>>>    - enable affected queue instances.
>>> 
>>> You also might think about how to ensure that installation of new execd
>>> hosts or re-installations will automatically get the fixed startup script 
>>> -
>>> T achieve this you'd changed the file
>>>
>>>    <sge_root>/util/rctemplates/sgeexecd_template
>>> 
>>> and find a means to ensure that with future patch updates your local
>>> changes
>>> do not get overridden.
>> 
>> thanks!!, that will certainly perserve me from some errors. :D
>> 
>>> The syntax "ulimit -a unlimited" does not seem to work (I tested it under
>>> bash on Linux and under sh on Solaris). See the respective man pages. It
>>> would be:
>>>
>>>    ulimit -l unlimited
>>>    (and all other limits you want to set)
>>> 
>>> and the really safe way would be to first set the hard, then the soft
>>> limit:
>>>
>>>    ulimit -H -l unlimited
>>>    ulimit -l unlimited
>>> 
>>> since a soft limit can't go beyond the hard limit.
>> 
>> Thanks again :)
>> 
>> 
>>> Neverthess I'm wondering this really the correct way? Doesn't Linux have a
>>> system wide login-defaults file where all these settings should be
>>> specified to ensure that programs started at boot time have a well defined 
>>> limit
>>> setting?
>> 
>> This is /etc/security/limits.conf, but unfortunately the daemons started
>> a boot time, fork directly from the init process and inherit therefore
>> the limits from init. Hence you have to overwrite it.
>> 
>> Thank you.
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
>> For additional commands, e-mail: users-help at gridengine.sunsource.net
>> 
>> 
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list