Well, I'm currently using the version from FreeBSD ports for 7.2. I'm not entirely sure how I would go about patching that port so as to maintain FreeBSD compatibility. Is there some way to make xrdp/Xvnc close the X11 instance upon termination of a connection--even if based on Xvnc's timeout for inactivity and then xrdp noticing this has occured and shut down any contingent X processes that would cause false-detects when sesman looks for an open display. Honestly, I'm open to any suggestions. I want to just have a web browser come up (which I have so far) upon connecting. But, I don't want there to be the possibility of any subsequent connections sharing that session where another user might have logged on. Is there a script like startwm.sh that executes every time someone connects and not just when its creating a new X11 session? Maybe then I could just kill the existing Firefox process being ran by that user.
I've already made the necessary changes to the parameters passed to Xvnc to manipulate display colours, prevent multiple users from sharing the same screen, and a few others tweaks. I'll probably end up having sesman cycle through several temporary user accounts to get around the login issue, but it still doesn't solve timing unused sessions out. It also requires that the xrdp.ini file gets re-parsed every time a new connection comes in (which, from what I can tell, it does--correct me if I'm wrong). -Nolte On Feb 4, 2010, at 12:37 AM, Jay Sorg wrote: >> Is there some way to have one user account that, for every new remote >> desktop connection, creates a new and unique desktop to work with? >> I want to set it up so that you login to the terminal server and it just >> pulls up a web browser that the user can interact with. However, the same >> PAM account should have multiple different possible sessions running >> concurrently so that each person connected has their own mouse, keyboard, >> and display. >> >> Can you point me in the correct direction with which to accomplish this? I'm >> assuming it's some sort of Xvnc parameter or Xserver configuration with >> regards to being able to resume sessions. Alternatively, there may be code >> within xrdp that is detecting whether or not a particular user has already >> logged in and simply connecting them to the existing back-end VNC display. >> I'd be willing to rewrite a portion of code or whatever to accomplish this, >> if necessary. I just need to know what the best point of entry is. >> -Nolte > > You will need to change one line of code. > You might have a problem running out of resources over time because of > disconnected sessions. > What version of xrdp do you want to use? > > Jay ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
