[FreeNX-kNX] FREENX: Performance of 2.0 client vs 1.0; open 2x Terminal Server/client mention (nx)
Tyler Ellis
tyler at inhousesupport.com
Tue Sep 5 08:40:14 UTC 2006
My 2.0 clients never work on windows or linux, its likely my distro
binaries or something like that?
Even 1.5 nxclient i do not download from nx i download from google
somewhere a version prior to this current release.
Linux 2.0 nxclient was installed on my debian, i downloaded 2x client
and it works i assume it is a 1.5 client.
I haven't seen the 2x server project but i suspect its management
features in gui's are the main benefit.
Anyhow rock on with the app! Thank you DEVS!
LROUFAIL at nc.rr.com wrote:
> I had this problem this weekend (with the newest nxclient) and found
> the solution in the FAQ:
>
> http://openfacts.berlios.de/index-en.phtml?
> title=FreeNX_FAQ/Problem_Solving
>
> 'Backingstore problem':
>
> Thorsten Sandfuchs found some issues concerning backingstore. Problem
> arouse as you try to connect to a 0.5.0 installation with no 2.0.0
> backend support and a 2.0.0-client. As Nomachine changed the behaviour
> of the backingstore-option. In 1.5.0-clients the client sends "always,
> when_requested" et all and freenx just passed this string to the
> nxagent-call. The new client now sends "backingstore=1" and the 1.5.0-
> nxagent issues a warning and an error with "no argument requiered for -
> bs" or with "Error: NX Agent exited with exit status 1.". You can read
> all his message here: Backingstore or 2.0.0-client and 1.5.0 backend
> and freenx-0.5
>
> Look at nxnode and in function 'node_start_agent()' after this line
>
> [ -n "$backingstore" ] && B="-bs $backingstore"
>
> add this lines:
> # backingstore = { "when_requested", "always", ... }
> [ -n "$backingstore" -a "$ENABLE_2_0_0_BACKEND" != "1" -
> a "$backingstore" != "1" ] && B="-bs $backingstore"
> # backingstore = 1 (new nxclient 2.0.0 doesn't send any strings in the
> option-string for backingstore anymore)
> [ -n "$backingstore" -a "$ENABLE_2_0_0_BACKEND" != "1" -
> a "$backingstore" = "1" ] && B="+bs"
> # backingstore = 1 and 2.0.0-Backend EXPERIMENTAL
> [ -n "$backingstore" -a "$ENABLE_2_0_0_BACKEND" = "1" ] && B="-bs
> $backingstore"
>
> This works using nxclient version 2.0.0-98.
>
>
>
> ----- Original Message -----
> From: Alastair Johnson <alastair at solutiontrax.com>
> Date: Monday, September 4, 2006 1:07 pm
> Subject: Re: [FreeNX-kNX] AGENT_STARTUP_TIMEOUT
> To: freenx-knx at kde.org
>
>
>> In your log I see:
>> NX> 1004 Error: NX Agent exited with exit status 1.
>>
>> This shows authentication has succeeded, but there has been a
>> problem starting
>> the session. Either there is a problem with nxagent starting, or
>> there is a
>> problem with the session starting which terminates nxagent early
>> and appears
>> in the logs as an nxagent failure.
>>
>> On Monday 04 September 2006 17:26, Carlos A. Sosa wrote:
>>
>>> Hi:
>>>
>>> Using latest FreeNX-0.5.0-10.1 rpm we found this error...
>>>
>>>
>>> As per:
>>>
>>>
>>> quote
>>>
>>>
>>> NX> 203 NXSSH running with pid: 1704
>>> NX> 285 Enabling check on switch command
>>> NX> 285 Enabling skip of SSH config files
>>> NX> 200 Connected to address: 192.168.1.12 on port: 22
>>> NX> 202 Authenticating user: nx
>>> NX> 208 Using auth method: publickey
>>> HELLO NXSERVER - Version 1.5.0-50 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: casosac
>>> NX> 102 Password:
>>> NX> 103 Welcome to: milmac user: casosac
>>> NX> 105 listsession --user="casosac" --status="suspended,running"
>>> --geometry="800x600x8+render" --type="unix-application" NX> 127
>>>
>> Sessions> list of user 'casosac' for reconnect:
>>
>>> Display Type Session ID
>>>
>> Options Depth
>>
>>> Screen Status Session Name ------- ----------------
>>> -------------------------------- -------- ----- -------------- --
>>>
>> ---------
>>
>>> ------------------------------
>>>
>>>
>>> NX> 148 Server capacity: not reached for user: casosac
>>> NX> 105 startsession --session="Prima" --type="unix-application"
>>> --application="xterm" --cache="8M" --images="32M" --link="adsl"
>>> --virtualdesktop="0" --rootless="1" --kbload="pc102/us" --
>>>
>> keymap="us"> --kbtype="pc102/us" --keybd="1" --nodelay="1" --
>> encryption="1"> --backingstore="never" --media="0" --
>> agent_server="" --agent_user=""
>>
>>> agent_password="******"" --screeninfo="800x566x8+render"
>>>
>>> NX> 1000 NXNODE - Version 1.5.0-50 OS (GPL)
>>> NX> 700 Session id: milmac-1043-7F0362F2A52115A546DC7698D772A249
>>> NX> 705 Session display: 1043
>>> NX> 703 Session type: unix-application
>>> NX> 701 Proxy cookie: b953ed0f63f40d9688a9c734e4d481cc
>>> NX> 702 Proxy IP: 127.0.0.1
>>> NX> 706 Agent cookie: b953ed0f63f40d9688a9c734e4d481cc
>>> NX> 704 Session cache: unix-application
>>> NX> 707 SSL tunneling: 1
>>> NX> 596 Session startup failed.
>>> NX> 1004 Error: NX Agent exited with exit status 1.
>>> NX> 1006 Session status: closed
>>> NX> 105 /usr/bin/nxserver: line 1077: 8172 Terminated
>>>
>> sleep
>>
>>> $AGENT_STARTUP_TIMEOUT Can't open
>>>
>>>
>> /var/lib/nxserver/db/running/sessionId
>>
> {7F0362F2A52115A546DC7698D772A249}:> No such file or directory. mv:
> cannot stat
>
>> `/var/lib/nxserver/db/running/sessionId
>>
> {7F0362F2A52115A546DC7698D772A249}':> No such file or directory
>
>>> unquote
>>>
>>> seems authorization problem....
>>>
>>> Any comment or suggestion will be welcomed.
>>>
>>> Tks in advance
>>>
>>>
>>> Carlos Sosa
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>> http://openfacts.berlios.de/index-en.phtml?title=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
>>> ________________________________________________________________
>>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>> http://openfacts.berlios.de/index-en.phtml?title=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
>> ________________________________________________________________
>>
>>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
> http://openfacts.berlios.de/index-en.phtml?title=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
> ________________________________________________________________
>
More information about the FreeNX-kNX
mailing list