Hi Colin,
Yes missing . was just a typo. I tried override.conf in
/etc/systemd/system/[email protected]/, still I do not see any
change in CPU utilization.
Container processes(sh and sha1sum) are using 50% CPU irrespective of CPUQuota
in ExecStart=/usr/bin/systemd-nspawn --quiet --boot --link-journal=try-guest
--machine=%i -n --property=CPUQuota=5%
I tried CPUQuota=5% under service section in override.conf instead of
ExecStart, still the CPU usage is 50%
And also I tried both in ExecStart as well as separate entry of CPUQuota=5%
under service section after ExecStart, still the CPU usage is 50%
Attached the systemd-cgls output for machine.slice.
Regards
Mahipal
On Thursday, 19 July, 2018, 10:41:14 AM GMT-4, Colin Guthrie
<[email protected]> wrote:
[email protected] wrote on 18/07/18 21:04:
> *override.conf* is effective when it is placed in
> */etc/systemd/system/[email protected]/*
I think you missed a . above:
/etc/systemd/system/[email protected]/*
>
> If I have file
> *[email protected] *in
> */etc/systemd/system.control/[email protected],
> *it is not effective, it's using the template file.
there is no system.control folder.
You should place a file called override.conf (or anything.conf) in a
folder: /etc/systemd/system/[email protected]/ if you
want the overrides defined in the .conf file to only apply to that one
machine.
All the best and HTHs
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited http://www.tribalogic.net/
Open Source:
Mageia Contributor http://www.mageia.org/
PulseAudio Hacker http://www.pulseaudio.org/
Trac Hacker http://trac.edgewall.org/
_______________________________________________
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
