Hi,
System is Scientific Linux 6.1
$ uname -an
Linux bertha.mnmms.local 2.6.32-131.17.1.el6.x86_64 #1 SMP Wed Oct 5 17:19:54
CDT 2011 x86_64 x86_64 x86_64 GNU/Linux
new install of xrdp from epel repository
$ rpm -qa |grep xrdp
xrdp-0.5.0-0.13.el6.x86_64
Rebooted box.
xrdp is running:
$ ps
Hi,
System is Scientific Linux 6.1
$ uname -an
Linux bertha.mnmms.local 2.6.32-131.17.1.el6.x86_64 #1 SMP Wed Oct 5 17:19:54
CDT 2011 x86_64 x86_64 x86_64 GNU/Linux
new install of xrdp from epel repository
$ rpm -qa |grep xrdp
xrdp-0.5.0-0.13.el6.x86_64
Rebooted box.
xrdp is running:
$ ps
OK, this morning I ripped everything xrdp or sesman related out of the
filesystem. That is, if the filename had xrdp or sesman in it, I deleted it.
I even rebooted (thus ruining my uptime track...oh well).
I've grabbed the git, configured with --enable-xrdpdebug compiled from that,
then inst
OK. It's working now. Turns out the problem relates to a subtle weirdness in
the gid that was assigned to the group 'tsusers' that sesman uses for group
level permissions (see sesman.ini).
Apparently (at least in redhat and derivatives) the gid of the tsusers group
has got to be number tha
