FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 01-21-2011, 01:43 PM
Alex Schuster
 
Default NX, FreeNX, Neatx, x2go?

Hi there!

I'm using various versions of NX to access remote servers. Normally I
use FreeNX, but sometimes NX from nomachine.org, and I also gave Neatx a
try, depending on which OS I am using - I do this with Gentoo, Fedora,
Ubuntu and openSUSE. This does not work too well. For example, I
regularly have to issue a 'nxserver --cleanup' to kill existing sessions
in order to be able to log in again. There are servers where I could not
log in with NX at all, although it used to work a while ago. Sometimes I
only have to try the login for several times, and suddenly it works if I
am lucky.
Sometimes I have no success at all, then I try another product. On
Gentoo, FreeNX seemed to work somehow, but only if I keep my session -
when I close the initial application (xterm), I have to clean the
session before I can log in again. Resuming works okay though.
And now I just setup a new Gentoo machine, and FreeNX does not work at
all - I can connect, the session seems to start, but no window opens.

As FreeNX seems to be dead, I thought I'd give x2go a try. Did anyone
have sucess with this? I don't even find proper documentation on how to
actually use it. According to [1], the Gentoo documentation is [2]. The
last comments state that there is no /etc/init.d/x2goserver script to
start the server. Looks like a bug to me, but maybe it is not needed at all?

What are these various x2go* commands for? Even the x2go wiki [3] does
not document the x2goserver* commands.

When I try to connect, I get this error message:

Verbindung fehlgeschlagen weird: Unable to connect:
/home/wonko/.x2go/ssh/socaskpass-Ds5896 Unable to connect:
/home/wonko/.x2go/ssh/socaskpass-Ds5896 Unable to connect:
/home/wonko/.x2go/ssh/socaskpass-Ds5896 Permission denied
(publickey,keyboard-interactive).

Then I specify my DSA key, I still have to enter my password, but I do
not get the error message. And that's it, syslog says x2gopgwrapper has
no tty present and no askpass programm was specified. I guess it wants
my SSH passphrase then.

Does it actually work for anyone? Does someone have pointers to a howto?
Is it actually worth to invest time here, or is x2go just not ready yet?
What would be the best solution? What do you prefer?

[1] http://www.x2go.org/index.php?id=6
[2] http://bugs.gentoo.org/show_bug.cgi?id=249600
[3] http://wiki.x2go.org/

Wonko
 
Old 01-21-2011, 02:37 PM
Paul Hartman
 
Default NX, FreeNX, Neatx, x2go?

On Fri, Jan 21, 2011 at 8:43 AM, Alex Schuster <wonko@wonkology.org> wrote:
> What would be the best solution? What do you prefer?

I haven't tried FreeNX, x2go or NeatX or any of those, but I'm using
nxserver-freeedition for years and using the official NX Client to
connect from remote machines (Linux and Windows). All of the features
work such as session suspending and resuming. I use public key login
on my machine and there was some trick to getting it working
initially. (I don't remember, but if you search for my name and
nxserver in this list's archives there should be a message about it
somewhere.)

I think that the other NX clients, such as QtNX, or things based on
libnxcl, usually only work to connect into a FreeNX server and not
with the official NX servers. Ideally I think the nx client version
should match the nx server version for best results.

nxclient contains a whole X server, which is really not necessary if
the client machine is already running X. Ultimately if your client has
X and ssh already, you just need nxproxy. Connect to server and run
nxagent and have a working session (there are shell scripts to do this
on platforms who have X but not nxclient, such as ARM). But you won't
get any of the special features like suspending and resuming,
printing, sound, etc.
 
Old 01-21-2011, 04:13 PM
Nikos Chantziaras
 
Default NX, FreeNX, Neatx, x2go?

On 01/21/2011 04:43 PM, Alex Schuster wrote:

[...]
As FreeNX seems to be dead, I thought I'd give x2go a try. Did anyone
have sucess with this? I don't even find proper documentation on how to
actually use it. According to [1], the Gentoo documentation is [2]. The
last comments state that there is no /etc/init.d/x2goserver script to
start the server. Looks like a bug to me, but maybe it is not needed at all?

What are these various x2go* commands for? Even the x2go wiki [3] does
not document the x2goserver* commands.


I use x2go, but unfortunately I installed the server on a Debian
machine, not Gentoo. There, the *.deb package installs and sets up
everything automatically and I can connect to it right away. I only run
the x2go client on Gentoo.


So I've no idea how to manually set it up. All I know is that it works
like a charm :-P
 
Old 01-22-2011, 10:49 PM
Stroller
 
Default NX, FreeNX, Neatx, x2go?

On 21/1/2011, at 2:43pm, Alex Schuster wrote:
> ...
> I'm using various versions of NX to access remote servers. Normally I
> use FreeNX, but sometimes NX from nomachine.org, and I also gave Neatx a
> try, depending on which OS I am using - I do this with Gentoo, Fedora,
> Ubuntu and openSUSE.

I'm not sure what you're trying to do, exactly, but it might be worth a look at xpra / Window Switch.

http://en.wikipedia.org/wiki/Xpra
http://winswitch.org/video/

Window Switch is basically a flashy GUI front end for xpra, but I think it supports NX and VNC on top of X11. Window Switch's version of xpra may not be compatible with the one in `x11-wm/parti`, as it has some extensions, but winswitch.org provides some ebuilds.

Stroller.
 
Old 01-24-2011, 11:15 PM
Alex Schuster
 
Default NX, FreeNX, Neatx, x2go?

Paul Hartman writes:

> On Fri, Jan 21, 2011 at 8:43 AM, Alex Schuster <wonko@wonkology.org>
> wrote:
> > What would be the best solution? What do you prefer?
>
> I haven't tried FreeNX, x2go or NeatX or any of those, but I'm using
> nxserver-freeedition for years and using the official NX Client to
> connect from remote machines (Linux and Windows). All of the features
> work such as session suspending and resuming. I use public key login
> on my machine and there was some trick to getting it working
> initially. (I don't remember, but if you search for my name and
> nxserver in this list's archives there should be a message about it
> somewhere.)
>
> I think that the other NX clients, such as QtNX, or things based on
> libnxcl, usually only work to connect into a FreeNX server and not
> with the official NX servers. Ideally I think the nx client version
> should match the nx server version for best results.

I'm also using using nxclient from nomachine.org.

I only tried nxserver-freeedition on an Ubuntu server where I had some
trouble running FreeNX. It worked well first, but then I started getting
some errors about a wrong 'bsize' or something. Ususally a few retries later
I can connect, but at the moment I can't. I did not investigate this further
yet because there are other servers in that LAN than I can use instead.

FreeNX is now working on my new machine. First I had to emerge xterm, which
was the custom command I wanted to execute. Stupid error, but a message that
the command could not be found would have been nice.
And then I had to change the DISPLAY_BASE in node.conf. Looks like when
running multiple instances of nxclient those values have to be different.

That was with Windows XP. Now I tried to connect from my Linux Desktop, and
got an error about the display :1043. I set it back to the default of :1000,
and it works again.
...
So it looks like when runing multiple clients, their servers need to have
different displays. Additionally, there is a timing problem, a workaround is
to add a sleep 4 in /usr/bin/nxnode right before the xrdb starts. I found
this tip somewhere on the web, noone added such a patch yet, probably
because FreeNX is dead.

> nxclient contains a whole X server, which is really not necessary if
> the client machine is already running X. Ultimately if your client has
> X and ssh already, you just need nxproxy. Connect to server and run
> nxagent and have a working session (there are shell scripts to do this
> on platforms who have X but not nxclient, such as ARM). But you won't
> get any of the special features like suspending and resuming,
> printing, sound, etc.

I never used sound or printing, although it might be nice. But
suspending/resuming sessions is really cool. I often run nxclient from my
Windows Notebook in the living room to run stuff on my linux desktop, and I
can shut down the notebook in between if I like.

Thanks for your input. I will consider nxserver-freeedition for the next
time I set up this stuff. FreeNX is dead, and I read that it is also a
genrally a little slower than the nomachine version. x2go looks not yet
ready, but I think I'll also try it when the next version arrives and I have
some spare time to paly around with.

Wonko
 

Thread Tools




All times are GMT. The time now is 06:41 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org