With libssh 0.6.0, x2goclient consumes 100% cpu on connection. The trigger for this is that ssh_select() was rewritten to use poll() instead of select(). poll() has a timeout in milliseconds, select() in microseconds. x2goclient requests a timeout of 500 microseconds which is getting rounded down to a timeout of 0 milliseconds for poll().
However, this still seems to point to some poor coding on the part of x2goclient that we're using such short timeouts. Why can't we just wait forever in ssh_select() in SshMasterConnection::channelLoop() ? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com _______________________________________________ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
