<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Nevermind. Found the problem. nxagent didn't get upated.<br>
<br>
Thanks,<br>
Brent<br>
<br>
Brent Davidson wrote:
<blockquote cite="mid45B5D9C6.2020507@texascountrytitle.com" type="cite">
<pre wrap="">I had a working installation of freenx 0.5.0 on Centos 4.4 with 2.1.0 NX
backend. I downloaded 0.6.0 and copied the files over the old fies and
now I cannot start an nx session. Log is below:
NX> 203 NXSSH running with pid: 464
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: <removed> on port: <removed>
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 1.5.0-60 OS (GPL)
NX> 105 hello NXCLIENT - Version 1.5.0
NX> 134 Accepted protocol: 1.5.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: root
NX> 102 Password:
NX> 103 Welcome to: <removed> user: root
NX> 105 listsession --user="root" --status="suspended,running"
--geometry="1280x800x32+render" --type="unix-gnome"
NX> 127 Sessions list of user 'root' for reconnect:
Display Type Session ID Options Depth
Screen Status Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------
NX> 148 Server capacity: not reached for user: root
NX> 105 startsession --link="modem" --backingstore="1" --nodelay="1"
--encryption="1" --cache="32M" --images="128M" --media="0"
--session="Test 1" --type="unix-gnome" --geometry="1280x766"
--kbtype="pc102/en_US" --screeninfo="1280x766x32+render"
NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL)
NX> 700 Session id: <removed>-1001-199CC9E7700F5FB45977C54D0029F8D7
NX> 705 Session display: 1001
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: bafa8267e1340c5b74de9f3e8f4ef3df
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: bafa8267e1340c5b74de9f3e8f4ef3df
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
NX> 1006 Session status: closed
/usr/bin/nxserver: line 1190: 9475 Terminated sleep
$AGENT_STARTUP_TIMEOUT
Can't open
/var/lib/nxserver/db/running/sessionId{199CC9E7700F5FB45977C54D0029F8D7}:
No such file or directory.
mv: cannot stat
`/var/lib/nxserver/db/running/sessionId{199CC9E7700F5FB45977C54D0029F8D7}':
No such file or directory
Killed by signal 15.
Any ideas?
Thanks,
Brent Davidson
Fabian Franz wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi List,
yes, there is a new release.
And yes it has been ages since a last release and it might even not be as stable and tested as one would expect after such a long time.
Anyway it works for me with 2.1.0 backend and 2.1.0 client on Linux and Windows.
Here is the ChangeLog including those of 0.5.0 and 0.4.5, because those were never properly released even though tagged correctly:
23.01.2007 FreeNX 0.6.0 "Juliana birthday edition"
* Opened the 0.6.0 branch.
* Added nxnode slave mode.
* General code cleanup.
* Huge cleanup of nxnode.
* Removed "no-x11-forwarding" from keys to allow client to use the
faster interactive sessions.
* Fixed nxsetup automatic testing of sessions and cleared up
explanations.
* Added support for NX 2.0.0 style nxclient dialogs.
* Support for NX 2.0.0 backend in nxloadconfig.
* Fixed cups printing (added username and password).
* Fixed one more stray tail process.
* Added example script for "load" based loadbalancing.
* Fixed spaces in parameters for NX Client 2.0.0.
(<a class="moz-txt-link-abbreviated" href="mailto:ssycplkbocve@spammotel.com">ssycplkbocve@spammotel.com</a>)
* Added version 2.1.0 support.
* Fixed LD_LIBRARY_PRELOAD default path in nxloadconfig.
* Fixed nxclient to work with 2.1.0 backend.
* Added autodetection of backend.
01.07.2006 FreeNX 0.5.0 "UKUUG 2006 Edition"
* Opened the 0.5.0 branch.
* Added load balancing.
* Completely removed support for 1.4.0 backend.
* Rootless mode is now the default.
* Reworked nxnode / suspend on connection failure should work now.
* Added support for "Running" sessions.
* Fixed --send command. (Emmanuel Blindauer <a class="moz-txt-link-rfc2396E" href="mailto:freenx@mooby.net"><freenx@mooby.net></a>)
* Fixed resume with nxclient >=1.5.0-106 for Windows.
* Fixed rootless sessions with Windows nxclient.
* Fixed keyboard issues by enabling the keybd channel.
* Fixed one more stray tail process and being able to
cleanup after a hopelessly failed reconnection. (i.e. agent died)
* Fixed detection of xauth / netcat. Added option to disable extra
checks.
* Fixed --terminate / --suspend when hostname has a '-' in it.
(Emmanuel Blindauer <a class="moz-txt-link-rfc2396E" href="mailto:freenx@mooby.net"><freenx@mooby.net></a>)
* ESD_NO_SPAWN is always set when ESPEAKER is set.
("Felipe Alfaro Solana" <a class="moz-txt-link-rfc2396E" href="mailto:felipe.alfaro@gmail.com"><felipe.alfaro@gmail.com></a>)
* Added perl replacement for 'rev' function on Sun OS 5.10.
* Fixed NODE_AUTOSTART to be unable to block sessions.
* Fixed stale sessions introduced by the new session handling model.
* Added usage of TCP NODELAY option.
* Fixed loadbalancing IP issues.
* Added --force-terminate to remove session info.
Fixed issue with suspend/terminate commands.
* Added correct errorcode 596 instead of 504.
* Implemented "round-robin" and "load" loadbalancing algorithms.
Cleaned up node.conf keys.
* Fixed help for --restart.
* Fixed session_running function, which fixes all remaining stale
session problems.
* Removed termination of nxagent in case of rootless mode.
(Fixes kontact without --nofork)
* Last minute fixes for new functions using rev.
* Added experimental last minute support for NX 2.0.0 backend.
(set ENABLE_2_0_0_BACKEND=1)
XX.XX.2006 FreeNX 0.4.5 "aKademy Edition"
* Made nxsetup more user-friendly and hopefully finally failsafe.
* Added --agent to nxnode/nxserver to allow easier debugging.
* Added addgroup/groupadd to nxsetup
* Added --ignore-errors support on nxsetup/nxloadconfig
* Added check for expect.
It happens to be my sisters 14th birthday today, so the release is named after her. But this is just a coincidence.
So: "Happy Birthday, Juliana!"
Now you might ask why there was such a long developer "down-time" and why now this sudden release.
For this sudden release you can thank the Fachschaft Informatik of University Karlsruhe, where I am a member, because they want to use it.
Why the long developer "down-time"?
Lets be honest here:
- I had some huge personal issues, which I had to solve first.
- I had a motivation gap.
- I had quite big monetary problems in the second half of 2006. Right after 0.5.0 was announced, but not released (because I forgot to write a release announcement ... :-( )
At the moment money is quite okay again, but if you want to donate something to me as a developer / person, feel free to do so via Paypal: <a class="moz-txt-link-abbreviated" href="mailto:paypal@fabian-franz.de">paypal@fabian-franz.de</a>.
I cannot and will not promise that development will start moving again, but if time permits it might very well be.
So I have got a question for you after you have tested the new 0.6.0:
What is the biggest issue you currently have with only FreeNX?
You can get the release from:
<a class="moz-txt-link-freetext" href="http://prdownload.berlios.de/freenx/freenx-0.6.0.tar.gz">http://prdownload.berlios.de/freenx/freenx-0.6.0.tar.gz</a>
Last but not least I want to thank all of those members that are still here on this list and are still using FreeNX despite all those nasty release issues.
cu
Fabian
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:
<a class="moz-txt-link-freetext" href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ">http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ</a>
Don't forget to check the NX Knowledge Base:
<a class="moz-txt-link-freetext" href="http://www.nomachine.com/kb/">http://www.nomachine.com/kb/</a>
________________________________________________________________
FreeNX-kNX mailing list --- <a class="moz-txt-link-abbreviated" href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/freenx-knx">https://mail.kde.org/mailman/listinfo/freenx-knx</a>
________________________________________________________________
</pre>
</blockquote>
<pre wrap=""><!---->
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:
<a class="moz-txt-link-freetext" href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ">http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ</a>
Don't forget to check the NX Knowledge Base:
<a class="moz-txt-link-freetext" href="http://www.nomachine.com/kb/">http://www.nomachine.com/kb/</a>
________________________________________________________________
FreeNX-kNX mailing list --- <a class="moz-txt-link-abbreviated" href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/freenx-knx">https://mail.kde.org/mailman/listinfo/freenx-knx</a>
________________________________________________________________
</pre>
</blockquote>
<br>
</body>
</html>