Re: [X2go-dev] Desktop sharing
Hello List, we are working on a nx-native Session-Shadowing/Desktop-Sharing feature which is almost ready for usage. But there are still some things that need to be done. I really hope you'll get the results soon. This feature will be available for all x2go installations (not only for LDAP + KControl + x2go sysrems). It is also planned to access the local, already running display and to let more than one person share your session. Until "now" we too have used x11vnc. best regards, Heinz --heinz-m. graesing-- -Ursprüngliche Nachricht- Von: Peter Puk Gesendet: 22.03.2010 22:19:16 An: x2go-dev@lists.berlios.de Betreff: [X2go-dev] Desktop sharing >As described here: http://www.x2go.org/index.php?id=72 >Quote: "You may share their displays to help them or to discuss your >projects." > >How can i share a desktop, or as i understand: >"login to an already running desktop, to support the current working user." > >In what way can i manage that. I'm already to access the "server" and >login to another user, but not take over an existing session. > >Ronnie >___ >X2go-dev mailing list >X2go-dev@lists.berlios.de >https://lists.berlios.de/mailman/listinfo/x2go-dev ___ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-dev] Desktop sharing
On Wed, 2010-03-24 at 18:40 +0100, Paul van der Vlis wrote: > John A. Sullivan III schreef: > > > Our solution was to use x11vnc. It is about the ugliest GUI I have ever > > seen and is a bear to configure but it is blazingly fast and allows > > access to display :0. We then chose xvnc4viewer as the viewer rather > > than Krdc. Krdc evidenced some instability when used with X11vnc. > > I've just tested Vino with Vinagre, this is the Gnome server/client for > VNC. You can connect to :0, looks nice, but it's slow. Yes - similar to Krfb/Krdc > > > If it would be helpful, I can post our procedure and set up to the > > list. > > Yes, I am interested. Do you maybe use the experimental "ncache speedup > feature"? I have never seen a fast VNC connection, even to localhost > it's real slow. We did not use it. All of our desktops are running on a limited number of very large VServer hosts - so we use virtual machine per virtual desktop. Since it is a shared memory environment, we were concerned about inflating memory use. We were not as concerned about performance because most of the traffic is literally inside the VServer host and does not even hit the Gb ethernet connections. > > Why don't you use xtightvncviewer or ssvnc? (x11vnc likes the tightvnc > protocol). We did not use ssvnc because we did not see it in the Lenny repository or in lenny-backports. It also has a very ugly interface even though very powerful. On the other hand, the xtightvncviewer interface was too minimal. xvnc4viewer was a nice balance for our environment - it looked good and gave ready access to options. We also did not have to specify :0 on the target - intuitive for techs but not for end users. Simply entering the target name without the display means fewer help desk calls. The biggest challenge for us was getting the right combination of the truly overwhelming x11vnc options. The combination we eventually settled on is: x11vnc -display :50 -shared -accept "popup" -gone "popup" -noxdamage -gui start,simple,tray=setpass There are some caveats here. Because the traffic is in an isolated data center with no users on the local network and because the traffic does not even tough the network in most cases, we did not implement ssl and we did not tunnel it through ssh to avoid the overhead. We also found xvnc4viewer did not support ssl (although we did not try very hard since we did not need it). We did want the users to set a password every time they started it. The noxdamage apparently compensates for a bug and provides much better performance when disabled. The one thing I would like to change is that the user must click on enable remote connections in the password dialog. I would like to default it to that. We tried the unlock and nodeny options but seem to confuse the command line parser. So far, we have been very pleased with the results but we just implemented it a couple of days ago. Hope this helps - John ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-dev] Desktop sharing
Paul van der Vlis píše v St 24. 03. 2010 v 18:40 +0100: > I've just tested Vino with Vinagre, this is the Gnome server/client for > VNC. You can connect to :0, looks nice, but it's slow. Give a try to Remmina: http://remmina.sourceforge.net/screenshots.shtml Works with vino server, it is faster and integrates to GNOME/Xfce panel. Though, I have not tried connecting to :0 regards, Milan Knizek knizek (dot) confy (at) volny (dot) cz http://www.milan-knizek.net - About linux and photography (Czech language only) ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-dev] Desktop sharing
John A. Sullivan III schreef: > Our solution was to use x11vnc. It is about the ugliest GUI I have ever > seen and is a bear to configure but it is blazingly fast and allows > access to display :0. We then chose xvnc4viewer as the viewer rather > than Krdc. Krdc evidenced some instability when used with X11vnc. I've just tested Vino with Vinagre, this is the Gnome server/client for VNC. You can connect to :0, looks nice, but it's slow. > If it would be helpful, I can post our procedure and set up to the > list. Yes, I am interested. Do you maybe use the experimental "ncache speedup feature"? I have never seen a fast VNC connection, even to localhost it's real slow. Why don't you use xtightvncviewer or ssvnc? (x11vnc likes the tightvnc protocol). With regards, Paul van der Vlis. -- http://www.vandervlis.nl/ ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Re: [X2go-dev] Desktop sharing
On Mon, 2010-03-22 at 22:19 +0100, Peter Puk wrote: > As described here: http://www.x2go.org/index.php?id=72 > Quote: "You may share their displays to help them or to discuss your > projects." > > How can i share a desktop, or as i understand: > "login to an already running desktop, to support the current working user." > > In what way can i manage that. I'm already to access the "server" and > login to another user, but not take over an existing session. Hi, Ronnie. I don't know a lot about these capabilities but I see that no one more knowledgeable has responded so I'll take my best shot :-) I believe X2Go currently supports their SpyGlass product. This would allow one desktop to see thumbnails of multiple desktops and, I assume, then zoom in on an individual one. I have never used it. NoMachine does have a shadowing facility. With it, one can open a new session to an NX server which shadows and existing one. It is slower than native NX as it uses VNC, I believe, to perform its magic. I do not believe this is implemented in X2Go yet but is imminent. In our environment, we opted to go for neither. Specifically for our environment, we found it was more practical to create a share/use desktop icon on the virtual desktop. Our users use their X2Go desktop as their primary work space. To have them leave it to open another X2Go client in order to shadow another user seemed more complicated than we needed and involved educating the users about choosing a shadow session rather than just letting them click on the icon, take the defaults we set, and work. Now, they simply click on the Share Desktop icon to allow others to see their desktop or View Another Desktop icon to connect to another desktop. All our users are remote but all their virtual desktops are on the same network. Thus, the performance is splendid and we are using native NX to bring the shared desktop back to the end user. Much faster than shadowing. The challenge for us was sharing display :0. We are using Debian Lenny desktops with KDE 3. Krfb is broken (as it is in Ubuntu, too) and, even when it does work is slow. Regular vncserver does not share display :0 but creates a new display. Our solution was to use x11vnc. It is about the ugliest GUI I have ever seen and is a bear to configure but it is blazingly fast and allows access to display :0. We then chose xvnc4viewer as the viewer rather than Krdc. Krdc evidenced some instability when used with X11vnc. If it would be helpful, I can post our procedure and set up to the list. Hope this helps - John ___ X2go-dev mailing list X2go-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev