[FreeNX-kNX] Server setup; no logging & command not found
Lucky0106
lucky0106 at msn.com
Sat Feb 22 18:19:27 UTC 2014
> Normally you'd be starting a GNOME or KDE desktop session. Do you
> have everything installed to run one?
I believe so... I mean, I can VNC in just fine and see my desktop
(although, the reason I'm looking for different solutions is because VNC
just doesn't cut it for me).
On 2/20/2014 12:16 AM, Les Mikesell wrote:
> On Wed, Feb 19, 2014 at 7:27 PM, Lucky0106 <lucky0106 at msn.com> wrote:
>> Hmm... I suppose I'm asking it to start an SSH session... Although the other
>> option appears to be the NX protocol, and that doesn't seem to work since I
>> don't think there even is a service listening on port 4000 on the host
>> machine (ps -Al doesn't seem to reveal such a process). I've been hearing
>> talk about how you can choose your DTE in NoMachine, but I have yet to see
>> such an option - I can't find anywhere to configure this in the client
>> profile setup.
> Normally you'd be starting a GNOME or KDE desktop session. Do you
> have everything installed to run one?
>
>> I just did a quick google of x2go, and I've seen quite a few people raving
>> about it... I almost wonder if I should move on at this point.
> Parts of it are the same nx libraries. The windows client has an
> advantage of being able to resize the screen on the fly.
>
>> If I may go a
>> bit off topic and ask, what are the differences that bother you?
> It just seems more fragile and likely to hang or fail to reconnect,
> but that may be partly because it tries to connect audio and client
> disks by default and partly because I don't understand how to
> configure it as well yet. I normally keep multiple sessions open to
> different servers from the same client and I know where to configure
> freenx so the display numbers won't conflict. In x2go you actually
> have to modify an executable script for that. Also, I frequently
> reconnect to sessions from different clients - and only very recent
> windows clients would resize corrrectly and earlier mac clients had
> the keyboard mapping wrong.
>
> Everything I needed worked pretty well with freenx (as packaged for
> CentOS in the centos-extras repository) and the 3.x versions of the NX
> client. However, the 3.x version won't work on OSX mountain lion and
> I don't particularly like the 4.x version. So, I'll probably switch
> to x2go when I have time to figure out all the options settings.
>
More information about the FreeNX-kNX
mailing list