Re: [HTCondor-users] Simplest way to change ulimit for all new jobs

[Rolf Seuster <seuster@xxxxxxx>]

Hi Sean,

this is probably because your job's shell is not a login shell. We worked around this
by adding a job wrapper to the workernodes:

USER_JOB_WRAPPER = /usr/libexec/condor/jobwrapper.sh

and

cat /usr/libexec/condor/jobwrapper.sh

#!/bin/bash -l
#
# Condor startd jobwrapper
# Executes using bash -l, so that all /etc/profile.d/*.sh scripts are sourced.
#
exec "$@"

Cheers, Rolf

On 2018-10-04 4:54 a.m., Sean Crosby wrote:

Hi all,

As I'm sure most of you are aware, there is a security bug with the RHEL kernels (CVE-2018-14634)Âwhich needs to be patched.

As there is no new kernel for RHEL 6 yet, the mitigation is to reduce the stack size ulimit (ulimit -HsÂ16000000)

I have tried adding the stack size ulimit to profile.d on the worker node, but jobs run via HTCondor are not picking this value up.

Does anyone have an easy way to ensure jobs (and their child processes) pick up the new stack size hard limit?

Jobs are being submitted via ARC-CE, if that helps.

Cheers,

Sean

--

Sean Crosby
Research Computing | CoEPPÂ| School of Physics

Senior System Administrator |ÂHPC | Research Platform Services

University of Melbourne

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/