You are not logged in.
Hi.
I think I configured everything correct in nx with shadowing etc. and am now trying to get shadowing running as a vnc substitute because it's way faster than vnc.
What works:
Opening an nx "Unix" session and connecting with another nx client with "shadowing" to the other session.
What works not:
Connecting to the running X server.
Documentation:
http://www.nomachine.com/documents/getting-started.php
NX offers the possibility to connect either to a local desktop (desktop sharing of the local native display), i.e.the X server running on the NX Node host machine; or to a NX session, named the master session, running on the NX Node host machine (session shadowing). These kinds of session, named 'shadow' in both desktop sharing and session shadowing, can be requested by setting Desktop -> Shadow in the NX Client GUI-> General tab. Upon the request of the end user, the server provides to the client the list of available sessions
It does not. It offers me only the already open "Unix"-nx sessions, not "the X server running on the NX Node host machine".
The logs on the nx server also show that there is no session, so it's no communication problem:
NX> 148 Server capacity: not reached for user: .*
NX> 105 listsession --type="shadow"
NX> 127 Sessions list of user '.*' for reconnect:
Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
NX> 148 Server capacity: not reached for user: .*
NX> 105 listsession --type="shadow"
NX> 127 Sessions list of user '.*' for reconnect:
Display Type Session ID Options Depth Screen Status Session Name
------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------
NX> 148 Server capacity: not reached for user: .*
NX> 105 listsession --type="shadow"etc.
Do you have some tips I can try?
Last edited by Cdh (2010-09-08 07:57:40)
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
If your using !Machine NX it should just work mostly out of the box, but I have not used it so don't know if it is just straight forward. Anyway you will probably need this info regardless of which NX you are using http://openfacts2.berlios.de/wikien/ind … owtoShadow and I don't think this issue exists anymore but some bed time reading http://fedoraforum.org/forum/showthread.php?t=209586
If your using freeNX it works after you patch it a bunch( Despite all the time on here I have heard it don't work ), I had it working about a year ago but I patched it a bunch using changes in the launchpad site but I don't remember what all needed to be done as I was patching to fix quite a few issues that still exist in the current arch package last I checked which was a while ago. You can browse around here https://launchpad.net/~freenx-team it may have been this one http://bazaar.launchpad.net/~freenx-tea … evision/86 ( 1+ year old update ) but I don't know if it depended on other changes. It got broken again on my workstation after an updated freenx package hit which I don't even know what the update was for since it didn't fix any of the issues I had patched; broken keyboard layout, broken Windows RDP, broken shadow sessions, etc. Maybe some of those are fixed now haven't had a chance to revisit it.
In case people say freenx doesn't do local session shadow despite the code commit I posted above here is a nice thread that says yeah it works now https://lists.launchpad.net/freenx-team/msg00166.html
Offline
I try to use nx-common 3.4.0-4, nxclient 3.4.0.7-1 and nxserver 3.4.0-6 from extra. It says this is from NoMachine but I don't know how the version numbers map to the ones I see in your links.
I have freenx 0.7.3-6 from extra installed too... It is needed by nxserver...
Is 0.7.3-6 >= 0.7.3+svn612-0freenxteam10?
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
then it sounds like you are using freeNX.
You need to follow the instructions here and create the nxshadowacl in /opt/NX/bin http://openfacts2.berlios.de/wikien/ind … owtoShadow
then you need to download and apply the diff file from here to nxserver in /opt/NX/bin http://bazaar.launchpad.net/~freenx-tea … evision/86
After that is done you should see your local session when you connect using the settings in the first link, however I tinkered with it last night and it would drop the connection when I tried to connect so there is probably another patch that needs to be applied, so if I have a some time today I will see what else may be breaking the connection.
Offline
Ok, the patch was it. Thank you very much.
But it is using vnc for shadowing with this patch, isn't it?
Because it's only a little bit faster than regular vnc.
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
if I understand the code right in nxnode yes, it just spawns off a x11vnc server in the local xsession then attaches to it. it may be possible to hack it to use XDMCP which would make it faster but that would take some looking into
Offline
Hm, ok. I don't know very much about nx, so I thought it somehow had some dirty hack to use the current X session as fast and responsive as "real" nx sessions...
฿ 18PRsqbZCrwPUrVnJe1BZvza7bwSDbpxZz
Offline
Without overly complicating the matter no, the only way it would work the way you want is if freenx were using XDMCP.
Really shadowing ruins the point of using NX, the point of NX is to allow consistent connection to a desktop regardless of the display point.
What you would be better off doing is using the nxclient locally to spwan an xsession and launch your window manager of choice then you can just disconnect when leaving and when you are someplace else use nxclient again to reconnect to that session, obviously you may still want the ability to have someone remotely access your session while you are using it eg to show your friend something, get help, etc.
This would be done by setting it in xinitrc to launch nxclient with a preconfigured configuration to launch your WM or login manager of choice. this way you would boot your computer, login, type startx and that would launch nxclient locally with a predefined configuration to launch nxserver locally connecting you to your window manager of choice, the same would hold true if your wanted to start it via init 5. Doing this way you would have the full added speed benefit of NX for remote access and locally it would be native speeds, however I don't know how it would act if you use compiz and the likes... You can get some ideas how this setup would work from this article http://www.gentoo-wiki.info/NXClient_as_desktop_manager
Offline