[FreeNX-kNX] Re: problems w/ freenx 0.7.0 and lastes nomachine sources on RHEL6.0

[hp]

not sure why but it comes back almost instantaneously now --don't even have a 
chance to go get coffee :( ..

[user1:~] ssh -X user1 at some.host "/usr/libexec/nx/nxnode --agent"
user1 at some.host's password: 
NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
NX> 716 Starting NX Agent ...
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Error: Aborting session with 'Cannot establish any listening sockets - Make sure 
an X server isn't already running'.
Session: Aborting session at 'Thu Jul 28 11:32:36 2011'.
Session: Session aborted at 'Thu Jul 28 11:32:36 2011'.
NX> 716 NX Agent exited with status: 1
NX> 1001 Bye.




________________________________
From: "chris at ccburton.com" <chris at ccburton.com>
To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
Sent: Thu, July 28, 2011 11:16:23 AM
Subject: [FreeNX-kNX] Re: problems w/ freenx 0.7.0 and lastes nomachine sources 
on RHEL6.0


hp <aput99 at yahoo.com> wrote on 28/07/2011 17:00:32:
 
> [user1:~/freenx] ssh -X user1 at some.host "/usr/libexec/nx/nxnode --agent"
> user1 at some.host's password: 
> NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
> NX> 716 Starting NX Agent ...
> 
> NXAGENT - Version 3.3.0
> 
> Copyright (C) 2001, 2007 NoMachine.
> See http://www.nomachine.com/for more information.
> 
> Info: Agent running with pid '39121'.
> Session: Starting session at 'Thu Jul 28 10:46:29 2011'.
> Info: Using alpha channel in render extension.
> Info: Not using local device configuration changes.
> error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
> Session: Session started at 'Thu Jul 28 10:46:29 2011'.
> 
> It just hang at the state... nothing came back for a while... 
> usually had to Ctrl-C to get out.
 
Well 

. . . as I stated, you will have to give it enough time, 
particularly if you are running over a WAN link, because 
it will be running without any compression. 

Set it going then go for coffee. 

Wait for a window or an error message . . .  

> BTW, ssh -X in and execute "xclock" does work.
 
Good, you proved ssh works ;) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20110728/35c53d93/attachment.html>