Hi,
Maybe this is absolutely irrelevant, but in the past I saw nearly 100%CPU
usage with Gnome. Changing to KDE solved the issue.
tamas
On 24 March 2013 16:18, Ralph Schmieder <mai...@janus.inka.de> wrote:
> Hi, all. I'm using xrdp latest git build on CentOS 6.4 compiled using the
> instructions at [1] 'building on CentOS 5.x'.
>
> Whenever I enable 'allow_channels=true' in the xrdp.ini to allow for
> clipboard functionality I see that xrdp-chansrv pegs the CPU at 100%. A
> subsequent session of another user does not show this behavior. If I
> disable channels, the problem is gone (of course). I *think* that I had the
> setting enabled before without seeing this phenomen but since a reboot it
> is very obvious and annoying.
>
> Was wondering what could potentially cause this and how to avoid it? I'd
> like to have the clipboard working (but could live w/o it temporarily)
>
>
> > [globals]
> > bitmap_cache=yes
> > bitmap_compression=yes
> > port=3389
> > crypt_level=low
> > allow_channels=false
> > max_bpp=24
> > fork=yes
> > # regulate if the listening socket use socket option tcp_nodelay
> > # no buffering will be performed in the TCP stack
> > tcp_nodelay=yes
> > # regulate if the listening socket use socket option keepalive
> > # if the network connection disappear without close messages the
> connection will
> > be closed
> > tcp_keepalive=yes
> > #black=000000
> > #grey=d6d3ce
> > #dark_grey=808080
> > #blue=08246b
> > #dark_blue=08246b
> > #white=ffffff
> > #red=ff0000
> > #green=00ff00
> > #background=626c72
> > #autorun=xrdp1
> > #hidelogwindow=yes
> > #bulk_compression=yes
> > # You can set the PAM error text in a gateway setup (MAX 256 chars)
> > #pamerrortxt=change your password according to policy at http://url
> >
> > [Logging]
> > LogFile=xrdp.log
> > LogLevel=DEBUG
> > EnableSyslog=1
> > SyslogLevel=DEBUG
> > # LogLevel and SysLogLevel could by any of: core, error, warning, info
> or debug
> >
> > [channels]
> > # Channel names not listed here will be blocket by XRDP.
> > # You can block any channel by setting its value to false.
> > # IMPORTANT! All channels are not supported in all use
> > # cases even if you set all values to true.
> > # You can override these settings on each session type
> > # These settings are only used if allow_channels=true
> > rdpdr=true
> > rdpsnd=false
> > drdynvc=true
> > cliprdr=true
> > rail=true
> > xrdpvr=true
> >
> > # for debugging xrdp, in section xrdp1, change port=-1 to this:
> > # port=/tmp/.xrdp/xrdp_display_10
> >
> > # for debugging xrdp, add following line to section xrdp1
> > # chansrvport=/tmp/.xrdp/xrdp_chansrv_socket_7210
> >
> > [xrdp1]
> > name=RDP
> > lib=libxup.so
> > username=ask
> > password=ask
> > ip=127.0.0.1
> > port=-1
> > xserverbpp=24
>
>
> Thanks,
> -ralph
>
>
>
> [1]
> http://www.xrdp.org/index.php?option=com_content&view=article&id=14:building-on-centos-5x&catid=2:documents&Itemid=7
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> xrdp-devel mailing list
> xrdp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xrdp-devel
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
xrdp-devel mailing list
xrdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xrdp-devel
