Is anyone using x2go on Centos - and if so, is there any reason to think about switching from freenx? The old NX client for mac was a powerpc binary and is no longer supported under mountain lion - and their new alpha release crashed my mac after an OSX update so I'm curious if there is anything better around. (And I didn't like the way the new mac version changed the screen scaling instead of resizing when you tried to change the window size, but maybe I just didn't know how to do it).
Les Mikesell writes:
Is anyone using x2go on Centos - and if so, is there any reason to think about switching from freenx? The old NX client for mac was a powerpc binary and is no longer supported under mountain lion - and their new alpha release crashed my mac after an OSX update so I'm curious if there is anything better around. (And I didn't like the way the new mac version changed the screen scaling instead of resizing when you tried to change the window size, but maybe I just didn't know how to do it).
I've tried to get it to work under CentOS5 - pretty much impossible. Will evaluate again once we move production to CentOS as FreeNX has some serious bugs when it comes to remote display forwarding and the only workaround is to use vnc.
On Tue, Sep 24, 2013 at 3:40 PM, isdtor@gmail.com wrote:
Les Mikesell writes:
Is anyone using x2go on Centos - and if so, is there any reason to think about switching from freenx? The old NX client for mac was a powerpc binary and is no longer supported under mountain lion - and their new alpha release crashed my mac after an OSX update so I'm curious if there is anything better around. (And I didn't like the way the new mac version changed the screen scaling instead of resizing when you tried to change the window size, but maybe I just didn't know how to do it).
I've tried to get it to work under CentOS5 - pretty much impossible.
You mean the client side? I'm more interested in the server, mostly on Centos6, with windows and mac clients. There are rpms for that but I haven't tried them yet.
Will evaluate again once we move production to CentOS as FreeNX has some serious bugs when it comes to remote display forwarding and the only workaround is to use vnc.
What kind of bugs have you found with freenx?
Will evaluate again once we move production to CentOS as FreeNX has some serious bugs when it comes to remote display forwarding and the only workaround is to use vnc.
What kind of bugs have you found with freenx?
Basically, if you are logged into a machine through NX and try to submit a job to our compute cluster via the queue/resource manager, GUI apps refuse to connect back to the NX display (e.g. machine:1008.0). We were able to reproduce this with simple utilities like xrdb, so it's not an issue with the apps in question. In turn, this always works when logged into the local machine (0.0) directly. Even xhost + does not help.
I didn't take any notes back then and found only very scant references on the web, but let's see. IIRC this was the most closely related issue I could find.
http://forums.opensuse.org/english/get-technical-help-here/install-boot-logi... (post #9) and http://forums.opensuse.org/english/other-forums/development/programming-scri... although it wasn't quite clear to me how the solution from link 2 was related to the problem in link 1.
On Tue, Sep 24, 2013 at 5:44 PM, isdtor@gmail.com wrote:
Will evaluate again once we move production to CentOS as FreeNX has some serious bugs when it comes to remote display forwarding and the only workaround is to use vnc.
What kind of bugs have you found with freenx?
Basically, if you are logged into a machine through NX and try to submit a job to our compute cluster via the queue/resource manager, GUI apps refuse to connect back to the NX display (e.g. machine:1008.0). We were able to reproduce this with simple utilities like xrdb, so it's not an issue with the apps in question. In turn, this always works when logged into the local machine (0.0) directly. Even xhost + does not help.
I guess the closest thing I've done would be browser windows in a selenium cluster run by a jenkins job. But I think they are really local windows with the remote control handled at some other level. I don't have any trouble with remote windows tunneled by ssh connections from my freenx session, though.
----- Original Message -----
From: "Les Mikesell" lesmikesell@gmail.com To: "CentOS mailing list" centos@centos.org Sent: Tuesday, September 24, 2013 12:18:34 PM Subject: [CentOS] x2go (vs. freenx)?
Is anyone using x2go on Centos - and if so, is there any reason to think about switching from freenx? The old NX client for mac was a powerpc binary and is no longer supported under mountain lion - and their new alpha release crashed my mac after an OSX update so I'm curious if there is anything better around. (And I didn't like the way the new mac version changed the screen scaling instead of resizing when you tried to change the window size, but maybe I just didn't know how to do it).
-- Les Mikesell lesmikesell@gmail.com
I'm using the latest beta2 NoMachine 4.0 client under Mac OS 10.8.5 to connect to two different NoMachine servers. One is an unlimited enterprise server(3.5.0) on RHEL 6.4 and the other is the free two concurrent user 3.5.0 version running on CentOS 6.4 offered by NoMachine. It works very well on both. You can change the NoMachine window to either scale the image or adjust the resolution of the window to be 1:1 on the fly.
David.
On Tue, Sep 24, 2013 at 5:52 PM, David C. Miller millerdc@fusion.gat.com wrote:
I'm using the latest beta2 NoMachine 4.0 client under Mac OS 10.8.5 to connect to two different NoMachine servers. One is an unlimited enterprise server(3.5.0) on RHEL 6.4 and the other is the free two concurrent user 3.5.0 version running on CentOS 6.4 offered by NoMachine. It works very well on both. You can change the NoMachine window to either scale the image or adjust the resolution of the window to be 1:1 on the fly.
I guess I'll give the new build a try eventually - just a little leery after having to track down and remove the previous version's kernel extensions in safe mode to get the mac to boot after the OSX update. What I want a screen resize to do is to keep 1:1 scaling and force the host to resize the desktop to match. The windows clients will only snap to a new size as they start up, but the old mac version would do a real resize (like linux) anytime.. I probably just missed how to do it in the new version.
-
David C. Miller -
isdtor＠gmail.com -
Les Mikesell