Hi Colin,
Yes missing . was just a typo. I tried override.conf in
/etc/systemd/system/systemd-nspawn@appscont.service.d/, 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
patlollamahi...@yahoo.co.in wrote on 18/07/18 21:04:
> *override.conf* is effective when it is placed in
> */etc/systemd/system/systemd-nspawn@service.d/*
I think you missed a . above:
/etc/systemd/system/systemd-nspawn@.service.d/*
>
> If I have file
> *systemd-nspawn@appscont.service *in
>
Hi Lennart,
Thanks for the response.
I am fairly new to systemd, may be I am not familiar with exact systemd
terminology.
I am starting the container using the command either "machinectl start
appscont" or "systemctl status systemd-nspawn@appscont" after "systemctl
daemon-reload"
override.conf
On Mi, 18.07.18 19:10, patlollamahi...@yahoo.co.in
(patlollamahi...@yahoo.co.in) wrote:
> Hi All,I am using systemd-nspawn(systemd version 237) to create a container
> in Yocto's embedded Linux environment on Cortex-A53
>
> Content of the file
>
>
>
Hi All,I am using systemd-nspawn(systemd version 237) to create a container in
Yocto's embedded Linux environment on Cortex-A53
Content of the file
/etc/systemd/system/systemd-nspawn\@.service.d/override.conf
is[Service]ExecStart=ExecStart=/usr/bin/systemd-nspawn --quiet --boot
