Hi, Thanks for all your efforts on x2go.
I've worked out that connecting to the same host (127.0.0.1, localhost, 10.n.n.n/192.168.n.n or <hostname>) is not currently supported.
I am struggling to find out how to track this issue so that when it is resolved I can return to x2go and drop neatx.
Appreciate any pointers to an issue or bug tracker.
Regards
-- πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα [The fox knows many things, but the hedgehog knows one big thing.] Archilochus, Greek poet (c. 680 BC – c. 645 BC) http://wiki.hedgehogshiatus.com
Hi there,
On Fr 22 Okt 2010 02:00:10 CEST Hedge Hog wrote:
Hi, Thanks for all your efforts on x2go.
I've worked out that connecting to the same host (127.0.0.1, localhost, 10.n.n.n/192.168.n.n or <hostname>) is not currently supported.
I am struggling to find out how to track this issue so that when it is resolved I can return to x2go and drop neatx.
Appreciate any pointers to an issue or bug tracker.
There is currently no debugging output in the code. For now, I
recommend to add debug lines in the original server code files
(x2goruncommand, x2gostartagent, etc.). For shell scripts you can use
the logger command (in Debian package bsdutils, refer to man logger).
Principally, you can also use that for Perl debugging just in
combination with a system call, but there might be a more elegant way
to do that.
Debugging of X2go server commands is really a need, I think, and I
recommend that for placing on the wishlist.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fri, Oct 22, 2010 at 10:54 PM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Hi there,
On Fr 22 Okt 2010 02:00:10 CEST Hedge Hog wrote:
Hi, Thanks for all your efforts on x2go.
I've worked out that connecting to the same host (127.0.0.1, localhost, 10.n.n.n/192.168.n.n or <hostname>) is not currently supported.
I am struggling to find out how to track this issue so that when it is resolved I can return to x2go and drop neatx.
Appreciate any pointers to an issue or bug tracker.
There is currently no debugging output in the code. For now, I recommend to add debug lines in the original server code files (x2goruncommand, x2gostartagent, etc.). For shell scripts you can use the logger command (in Debian package bsdutils, refer to man logger). Principally, you can also use that for Perl debugging just in combination with a system call, but there might be a more elegant way to do that.
Debugging of X2go server commands is really a need, I think, and I recommend that for placing on the wishlist.
Thanks Mike.
From reading the list archives I thought this 'client+server on localhost' issue was known and being worked on - so I really just wanted to 'follow' the issue to know when to use x2go. If this localhost issue still needs debugging then I'm happy to give it a shot.
Could someone clarify the current state?
Best wishes
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-- πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα [The fox knows many things, but the hedgehog knows one big thing.] Archilochus, Greek poet (c. 680 BC – c. 645 BC) http://wiki.hedgehogshiatus.com
-
Hedge Hog -
Mike Gabriel