Seems you are not going to give up. =)<br><br>I must say it isn't an easy task. I know because I am writing a new server.<br><a href="https://code.edge.launchpad.net/~marceloshima/tacix/0.1">https://code.edge.launchpad.net/~marceloshima/tacix/0.1</a><br>
<br>Let me try to explain how it should work:<br> 1 - Create the options and authorization on the server.<br> 2 - Run NXAgent on the server.<br> 3 - Pass the authorization and options from the server to the client.<br> 4 - Create the options of the client.<br>
5 - Run NXProxy on the client.<br> 6 - NXProxy should communicate with NXAgent successfuly.<br> 7 - You have a running session.<br><br>The most difficult part is to create the options for NXProxy based on the information created<br>
for the NXAgent.<br><br>
So the most important task is to create the communication protocol.<br>I was thinking in using dbus or soap. But for now I am using the protocol nxclient/nxserver<br>uses.<br><br>I think the easiest way for you to accomplish what you are trying to do, is to hack on the<br>
client I am writing and make it compatible with usermode FreeNX. Or use the tacix server.<br> * Usermode FreeNX is the mode Fabian made that you can log in directly into the<br>user account and start the session from there.<br>
The client I am writing uses python-paramiko for ssh library, so it provides support<br>for ssh-agent and others.<br><br>For the client you can take a look at:<br><a href="http://bazaar.launchpad.net/~marceloshima/tacix/0.1/annotate/head%3A/tacix/client/TXClient.py">http://bazaar.launchpad.net/~marceloshima/tacix/0.1/annotate/head%3A/tacix/client/TXClient.py</a><br>
and<br><a href="http://bazaar.launchpad.net/~marceloshima/tacix/0.1/annotate/head%3A/server/tacix-client">http://bazaar.launchpad.net/~marceloshima/tacix/0.1/annotate/head%3A/server/tacix-client</a><br><br>Hope this helps.<br>
Shima<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Joshua Kinard</b> <span dir="ltr"><<a href="mailto:joshua.kinard@sdc-world.com">joshua.kinard@sdc-world.com</a>></span><br>
Date: Wed, Jun 24, 2009 at 2:50 PM<br>Subject: [FreeNX-kNX] nxproxy usage?<br>To: "<a href="mailto:freenx-knx@kde.org">freenx-knx@kde.org</a>" <<a href="mailto:freenx-knx@kde.org">freenx-knx@kde.org</a>><br>
<br><br>
<div>
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Having a blonde moment here, but I'm attempting to run the commands in an ssh shell and seeing how far I can get. Figured out (somewhat) how to start the agent:</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">nxnode --startsession <ENTER></font></div>
<div dir="ltr"><font size="2" face="tahoma"><bunch of silly options></font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Then it prints out stuff that indicates that the session is running and sits there. Now I have roughly ~60 seconds to get nxproxy running before the agent gives up, packs its bags, and goes home. But running nxproxy
is confusing me, and the directions aren't exactly clear on what I should be passing it.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="Tahoma">Quote from </font><a href="http://www.nomachine.com/ar/view.php?ar_id=AR03C00171" target="_blank"><font size="2" face="Tahoma">http://www.nomachine.com/ar/view.php?ar_id=AR03C00171</font></a><font size="2" face="Tahoma">:</font></div>
<blockquote dir="ltr" style="margin-right: 0px;">
<div dir="ltr"><font size="2" face="Tahoma">8. Then in another shell (or in background), please invoke nxproxy with the proper parameters. Parameters can be passed on the command line or in the options file, usually created in the session directory, in $HOME/.nx:</font></div>
<div dir="ltr"><font size="2" face="Tahoma"> nxproxy -S options=path to options file/options:Session display</font></div>
</blockquote>
<div dir="ltr"><font size="2" face="tahoma">The only folder I have in ~/.nx while the agent is running is in the format of C-$HOSTNAME-$DISPLAY-$UNIQUEID, where $DISPLAY and $UNIQUEID come from the params I passed to nxnode --startsession. The example given
for nxproxy indicates it's looking for a folder that starts with S-, not C-. If I pass it the C- path + /options, it notes that it is ignoring several options, then quits after trying to bind to the same TCP port that the agent is already sitting on, which
causes it to error out.</font></div>
<div dir="ltr"> <br></div>
<div dir="ltr"><font size="2" face="tahoma">Now, this is assuming nxproxy should be run from the server ssh session, as that's what the instructions seem to imply. Am I supposed to be switching back to the client, where nxproxy is available, and running it
from there, copying (as fast as I can) my parameters from the server, creating the S-$HOSTNAME-$DISPLAY-$UNIQUEID directory, populating the options file, then launching nxproxy? If so, that will be difficult to scriptify in bash or something.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">The way I'm reading the documentation, is that nxnode --startsession and nxproxy get run on the server side, and somehow, another utilitiy runs on the client to connect. Right now, my environment is a RHEL5 system
as the server, and a Debian Etch-based thin client as the client. The thin client only has the standard NoMachine nxclient on it (thus no nxproxy), while the RHEL5 has nx and the freenx server RPM.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">How I'm currently kludging things:</font></div>
<div dir="ltr"><font size="2" face="tahoma">1. Sitting on the thin client, doing dual SSH sessions to the server with X11Forwarding enabled. One session invokes nxnode --startsession, and feeds it some values that I partially autogenerate quickly by hand (i.e.,
run a script, copy+paste output). The agent invokes and starts a session.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">2. Second session to the server invokes nxproxy. This is where I'm stuck. According to the documentation, nxproxy is supposed to load here, and then I switch back to session 1 and log off of the ssh session, thus
dropping back to the client. What I'm supposed to do after this, I'm, not sure. NX's guide ends at this point.</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Anyways, long read, but if anyone has pointers as to what I'm doing wrong, let me know. Still got ~4 more hours to crack at it, though!</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">Thanks!</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div><font color="#888888">
<div dir="ltr"><font size="2" face="tahoma">Joshua Kinard</font></div>
</font></div>
<br>________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br>
Don't forget to check the NX Knowledge Base:<br>
<a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
<br>
________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br></div><br>