I have a Xubuntu 14.04 Server here that runs xrdp to have a couple of users connect to it.
Now there's one problem: users who access this server via RDP from Windows thin clients often use the "X" to close the RDP session (therefore disconnect but not logout).
I know there are some options in sesman.ini to deal with that kind of behaviour, but as the manpage says, those options are currently ignored (and have been for years).
The options which would solve my problems are:
KillDisconnected
DisconnectedTimeLimit
IdleTimeLimit
Now I need to hack something that deals with disconnected sessions. My first thought was to just kill all remote users who are disconnected – but I don't know how to get that information which sessions are disconnected.
So… how do I find disconnected sessions?
Or: is there already any preferred way to deal with disconnected sessions?
Best Answer
Here is a way to obtain a list of disconnected xrdp sessions. It relies on the fact that the xrdp server is, in normal X session manager usage, the only client that establishes a TCP connection to the Xvnc X Window System display server. When an xrdp session is active, the associated Xvnc display server has two TCP connections, one in the ESTABLISHED state, and the other in the LISTEN state. That looks something like this using the lsof(1) program.
If the user of the remote session abandons it by closing the RDP connection (or, in the case of an Apache Guacamole RDP session, by closing the browser window) it looks something like this:
Notice there's no ESTABLISHED connection on this disconnected Xvnc display server process. So, any Xvnc process that's only listening is a disconnected session.
Here's a shell script (named
lsdisconnected
) that displays the PID and USER for each disconnected remote session. It uses lsof(1) and gawk(1) to implement the connection logic.This is a handy way to find disconnected remote desktop sessions; it works immediately upon disconnection, without needing to use an idle time.
For those who may not be familiar with lsof(1) here's an explanation of the command line parameters in this example.
-b -w
avoids lsof kernel waits. They're not needed here.-n
avoids DNS lookups for hostnames.-c /^Xvnc$/b
looks for processes with the exact command name Xvnc, using a regex.-a
tells lsof to use AND, not OR, when filtering.-iTCP:5900-5999
filters by TCP ports numbered 5900 - 5999, the ones used for X display connections.)