On 01/08/2018 06:31 AM, Rajil Saraswat wrote:
On 01/07/2018 10:41 PM, Stéphane Graber wrote:
On Sun, Jan 07, 2018 at 08:46:40PM -0500, Stéphane Graber wrote:
Given that it's reporting a scheduler problem, it's likely that one (or more)
of the 4 keys above at the problem as some of those actions won't be
allowed in a container.
You could edit the unit and comment those, then run "systemctl daemon-reload"
and try starting the service again.
If that does the trick, then you should be able to make this cleaner by
using a systemd unit override file instead.
Commenting out the following worked,
#IOSchedulingClass=realtime
#IOSchedulingPriority=2
#CPUSchedulingPolicy=rr
Sure, it works.
Thank you, Rajil, Stéphane, you help me fine as I have the same problem.
But at the cost of IOSchedulingClass not realtime.
This may be a problem with freeswitch.
Is there a way to parametrize the container so that
IOSchedulingClass=realtime is OK ?
_______________________________________________
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
