[X2go-dev] How to track an x2go issue/bug?

[Mike Gabriel]

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 at das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb