you should check if any proccess/sub-proccess of xrdp-sessvc is binding the
port (should use sudo netstat -apn).
that was a bug in xrdp-sesman, which fixed recently
(https://github.com/FreeRDP/xrdp/commit/75f4c3ca584b30b6e7f44dfec0da0845de43a166)
--
View this message in context:
http://xrdp-de
t: Re: [Xrdp-devel] Improving XRDP performance
>
> Oh, BTW, if you want to turn it on to see the server side CPU
> savings,
> uncomment rdpXvInit(pScreen) in rdpmain.c.
>
> To get back to the original question for this thread, we could still
> do everything in software and use this extension to k
