On 6/29/2010 12:00 AM, Murtaza Munaim wrote:
On 6/28/2010 8:19 PM, Robert Seward wrote:On Mon, Jun 28, 2010 at 5:46 PM, Murtaza Munaim<mur...@gmail.com> wrote:On 6/23/2010 9:42 AM, Jay Sorg wrote:Hey guys. So I was looking at the code for xrdp. I know I need to have the connection between sesman and xrdp be maintained for the entire session, and then have sesman kill the session when xrdp sees a user disconnect. I could go looking through all the code, but I was just wondering if someone knew where in the code xrdp connects/disconnects from sesman. ThanksHi Murtaza, The connection goes up in file xrdp/xrdp_mm.c function xrdp_mm_connect It uses an object called struct trans to talk to sesman. trans_connect is the call to do the connect. The connection goes down in xrdp_mm_process_login_response self->delete_sesman_trans = 1; will cause the disconnect later. Then on the sesman side, I have to look more. JayHey Jay. Let me know what you remember/find from the sesman side. Also, the enviornment I was running xrdp before was using xrdp-0.4.0~dfsg as the main xrdp server. I downloaded the cvs version of xrdp, and did the standard make && make install and it worked fine, the compiling and installing at least. Then when I rdesktop'ed like I usually would have. As it was connecting, it would get to "connecting to 127.0.0.1 5910". Then I would get an error - problem connecting. Is there a debug or verbose mode to xrdp or something of the like? What could be different between the two version to break it? -Murtaza ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-develHey Murtaza, I don't know if you are interested, but I did pretty much want you are trying to do. However, the changes were done to xrdp 0.4.1, and there are a number of other changes that I made that you may or may not want. I haven't had time to try to submit all the patches against the latest CVS, but you can take what I have if you want. RobertRobert, Could you briefly summarize the changes you made? And send me a tarball of your patches? That would be awesome. Thanks -Murtaza
Hey Guys.Robert: If you have time, could you send me the patches you have written so I can see what you did? Thanks a bunch
Jay: I had a question about how sesman works. So I see that sesman has two version of scp(Sesman Control Protocol). I was wondering why that is. Also, as mentioned in the old idea about communication from xrdp to sesman, I have a thought on that. I see that sesman keeps a list of disconnected sessions from a particular user. To add this functionality of session deletion, would it be cleaner to instead, if the option is enabled, kill any sessions with sesman the moment that a disconnected session is added to sesman. That way, everytime a disconnected session is added, the session is killed automatically. Would this work? And to kill the particular session, would I use the session_kill function in session.c? Could this also be extended to a timeout feature being added so that when a disconnected session is added to the list, if it has a particular time, then I kill that as well.
Thanks a lot guys. -Murtaza
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
