|
Grettings from sunny New-Mexico . Goal : To be able to login ( not share the desktop, but actually claim the session) from remote locations. The best example for this is Microsoft's Remote Desktop Protocol and its client, " Remote Desktop Connection ". Here's the shortest summary for a long process I've been through. thank you for reading. I've tried : Vino - will allow to view display :0 , a user needs to be logged in order for it to work, it is possible to run it as a service and that way eliminate the need for an active session to be in place , have not tried running it as a service yet, due to the fact the it will ( as VNC does) , not " steal " the session, but will only shadow the session. TightVNC server - No go, will act as a " Terminal Server" , if the session a user left was attached to :0 , then I'll login to :1 or :2 and onward . XRDP - A server that uses Microsoft's RDP client to connect to a VNC session on Linux, it was a great find, but all in all, it's a VNC session as TightVNC would be . Freenx - Fast and reliable, and probably the one I'll stick with if I will not find a 100% satisfying solution . It will let me "roam" on the same remote session it'll create, but, it will not let me in to display :0 . I've been using this one for super-fast remote sessions to remote servers that do not run an actual desktop rather only the X11 libs, works like a champ. But its a different story with a computer that has an actual desktop. X11vnc - the only one I found that will actually let me in to my own session, the downfall is that it will not "steal" the session, as would RDP, but, it will shadow the session, ( as VNC does), thus , compromising speed. I'm aware of scripts outthere that would at-least lock the local screen when X11vnc is initiated , the need for that is vastly understood I'm sure. It is getting a bit frustrating, because most people I ask for an RDP ( and it's logic) like solution in Linux, would immediately reply " use VNC ". Oh well, its not the same. I did find a smart trick to combine X11VNC and TightVNC as servers and then use NX clinet to remote in to : 0, it does work, but sadly the speed was sub-par, not a practical solution. I was hoping for the NX speed on that one, Ended up getting the slowest result. Speed is subjective, so I'll say that typing a letter in the terminal took 5 seconds to show up, as for the graphical performance, was nearly impossible to work. I'm aware that there are some tweaks to speed up X11VNC's performance, and am working on it. But, in case I'm missing on something some of you may know, I'm sending this one out. Thank you, Guy |
_______________________________________________ Linux-il mailing list [email protected] http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
