Hi! On Mi 02 Jan 2013 17:25:59 CET wrote:
OK it seems that I am doing New Science. No one can help. On Thu, Dec 27, 2012, at 15:29, [1][email protected] wrote: Anyone home? On Mon, Dec 24, 2012, at 9:27, [2][email protected] wrote: Couple issues fellers: I have PyHoca set to Log In Automatically and Start New Session Automatically, but it is doing neither when I start it.
I am currently working on this. There are command line switches that activate this feature, but I plan to make autostart/autoconnect available without extra cmdline options. See the pyhoca-gui man page: --start-on-connect, --resume-on-connect and --auto-connect.
Also when I tell PyHoca to connect to one server it always always says, "The authenticity of host [hex] can't be established. Are you sure you want to continue connecting?" When I ssh to this host it always asks the same thing. Why is the system never put it in known_hosts? My other x2go system doesn't have this problem.
I also have this issue from time to time with several hosts. My guess is that it is related to some entry in known_hosts. Does the issue go away with an empty known_hosts file? Of course, this is not a solution. I am just curious, if it helps.
Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: [email protected], http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpx2DXjU_np7.pgp
Description: Digitale PGP-Unterschrift
_______________________________________________ X2Go-User mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-user
