On Fr, 29.05.20 00:31, Nuno Reis (nr...@wavecom.pt) wrote:
> > I've noticed that if I give the same CPUScheduling options to the
> > 'systemd-nspawn@'.service service on the Fedora 32 hosting
> > system I don't have the following error anymore in the container:
> > Failed at step SETSCHEDULER spaw
Hi guys.
I'm new to this mailling list so I hope this is a good place to ask this
type of stuff.
I'm trying to have a nspawn container to run freeswitch with some realtime
settings set at service level and I'm facing some permission issues as I
explain bellow. When trying to search for related is
