[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] cgroup setup with centOS7/systemctl?

Hi Thomas,

I think this would now all go into site-local overrides for the HTCondor unit files.

If you find yourself doing anything cgconfig related, you're fighting a 100% losing battle as time goes forward.

Going off memory, I think you can simply set in the condor config:


and you're done -- no other services to run.

If, for example, you want all of HTCondor to have a limit of 16GB of RAM, you would create the following directory (see https://www.freedesktop.org/software/systemd/man/systemd.unit.html):


and then create a file /etc/systemd/system/condor.service.d/99_local.conf with the following contents:


(see https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html).

While this is indeed a new approach to learn, the upside is that this works across the entire range of system services -- and the config file format / rules is shared with huge swaths of the system!


> On Mar 13, 2017, at 4:51 AM, Thomas Hartmann <thomas.hartmann@xxxxxxx> wrote:
> Hi all,
> with /etc/cgconfig.conf being deprecated under CentOS7/systemctl, I
> wonder if there is already a 'canonical' approach on how to setup/run
> cgroup configs for Condor under systemctl?
> Would be creating an overall unit for condor (or setting resources via
> systemctl set-property for condor.service) the way to go?
> I suppose jobs will be in the condor.service cgroup - would additional
> steps be necessary for setting any job resources (systemd-run?)?
> Cheers and thanks,
>  Thomas
> _______________________________________________
> 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/