[slurm-users] What's the best way to suppress core dump files from jobs?

Patrick Goetz pgoetz at math.utexas.edu
Thu Mar 22 07:10:30 MDT 2018

Or even better, don't think about it.  If you type

   sudo systemctl edit slurmd

this will open an editor.  Type your changes into this and save it and 
systemd will set up the snippet file for you automatically (in 

On 03/21/2018 02:14 PM, Ole Holm Nielsen wrote:
> Hi Michael,
> Thanks for your friendly advice!  I keep forgetting about Systemd 
> details, and your suggestions are really detailed and useful for others! 
>   Do you mind if I add your advice to my Slurm Wiki page?
> /Ole
> On 21-03-2018 16:29, Michael Jennings wrote:
>> On Wednesday, 21 March 2018, at 12:08:00 (+0100),
>> Ole Holm Nielsen wrote:
>>> One working solution is to modify the slurmd Systemd service file
>>> /usr/lib/systemd/system/slurmd.service to add a line:
>>>    LimitCORE=0
>> This is a bit off-topic, but I see this a lot, so I thought I'd
>> provide a friendly warning.
>> The "right" systemd way to do this is either to put a new unit file in
>> /etc/systemd/system/ which will completely override the one in
>> /usr/lib/systemd/system/, *OR* you can create
>> /etc/systemd/system/slurmd.service.d/core_limit.conf and put ONLY the
>> following in it:
>>    [Service]
>>    LimitCORE=0
>> This will *supplement* the SchedMD unit file rather than causing you
>> to have to maintain a patched/modified version until the end of
>> time. :-)
>> Opinions on systemd are varied and often rather passionate, but one
>> thing they did get right (IMHO) is making it easier for distribution
>> providers, software packagers, and system engineers to all have a say
>> in how things are configured without stepping all over each other's
>> toes!  ;-)

More information about the slurm-users mailing list