[FreeNX-kNX] freenx and real X-session

[Marcelo Boveto Shima]

Actually, it is possible to shadow the local X.
Download the following diff and apply to nxserver. Then you must select
shadow on your nxclient session, it will offer to shadow the local X.

http://bazaar.launchpad.net/~freenx-team/freenx-server/ubuntu/revision/86

But shadow sessions is not as fast as a native nx session.
Hope this helps.
Regards.
Shima

On Fri, Jan 30, 2009 at 2:50 AM, Anton <warm at stack.ru> wrote:

> Ok. Thank You very much for full answer. I'll try to use 1.
>
> On Fri, 30 Jan 2009 10:33:38 +0600
> Mario Becroft <mb at gem.win.co.nz> wrote:
>
> > Anton <warm at stack.ru> writes:
> >
> > > Good day.
> > >
> > > I suspect that my question was asked many times befor but I could not
> to find any answer at google.
> > >
> > > I have real X-session in my work desktop (gdm to login + icewm). I lock
> my desktop by the xlockmore and go
> > > home. At home I try to connect to my work desktop by nxclient. Always I
> get new session or suspend this
> > > new session and then I can detouch it back. But I want to get into my
> real X-session is it possable ?
> > > How ?
> > >
> > > I tried to use shadowing but it does not work or it is not what I want.
> I find at google and docs that I
> > > should use KDE or Gnome to get their session detouched but I do not
> want use this heavy DE :-). I need to
> > > use my usual desktop enveroment.
> >
> > When you use nx, you either create a virtual display that you login to,
> > or you directly run an application. In both cases, this has nothing to
> > do with any existing X server that might be running on your machine, and
> > so will be completely irrelevant for accessing your existing session
> > running locally on the machine.
> >
> > There are two ways you could achieve what you want:
> >
> > 1. When locally on your machine, always run nxclient and login to a nx
> > session instead of directly using the X display on the machine. Then you
> > can login to this same nx session remotely.
> >
> > 2. Continue to run X locally as you are now, and use some special
> > software to mirror the display remotely. The easiest way to do this is
> > probably with a tool called "x11vnc" (google it). In theory nx's session
> > shadowing feature could be used for this, but it does not provide a way
> > of actually doing this as normally configured. The only problem is,
> > x11vnc is not particularly fast due to the way it works.
> >
> > 3. The third way is actually the same as 2., but if you are using Xorg
> > as your local X server, there is a module directly providing a VNC
> > server mirroring your local screen. This works like 2., but will be a
> > bit faster. You could look up on the web how to configure this feature.
> >
> > When using option 2 (or 3) you can use nxclient to login to the VNC
> > session--but it would probably be just as good to simply use vncviewer
> > for this (the main benefit of nx here is that it would provide
> > encryption which is not normally available with vnc).
> >
> > If you want good performance when accessing remotely, I suggest option
> > 1. But if you just occasionally need to access the session remotely and
> > performance does not matter so much, then option 2 might be the best.
> >
> > --
> > Mario Becroft <mb at gem.win.co.nz>
>
>
> --
> Anton [WARM-RIPE]
> Stack ltd division head
> tel. 8 (3822) 555-797
>
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>    Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
>         Don't forget to check the NX Knowledge Base:
>                 http://www.nomachine.com/kb/
>
> ________________________________________________________________
>       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>      https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090130/9a638604/attachment.html>