On Wednesday 2012-06-06 08:07, Mike Gabriel wrote: > >> 4) Once installation is is complete, several things do not work as >> expected... >> >> >> 4.1) File permissions are incorrect: sudo: /etc/sudoers.d/x2go is mode 0644, >> should be 0440
What is the rationale for requiring 0440? >> 4.2) On a server with gnome installed, but no complete X installation, >> creating a connection fails (session terminates during session start >> procedure >> with no clear error message). > > About the runlevel issue, I am not sure. Is SSH started on runlevel 3? I guess > so. Hmmm... Once you can login via SSH, X2Go login should normally work as > well... I also think that the x2go software needs to convey error messages better. Like, when the session sqlite db is not writable, you will only know if you actually perl -d the relevant scripts, because stderr is never relayed to the user and his login GUI, for example. >> 4.3) In the install from source documentation, reference is made to int >> scripts needed which should run 'x2gocleansessions' in background/daemon >> mode. >> No such script is installed but connections still can function (at runlevel >> 5, >> see point 4.2 above). > > An example script can be this: > http://code.x2go.org/gitweb?p=x2goserver.git;a=blob;f=debian/x2goserver.init > > If that is not in the RPM x2goserver package, then this needs fixing. That init script requires love. Using killall looks like a Thor's hammer to kill a fly. (Luckily users with systemd don't have that problem.) _______________________________________________ X2Go-User mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-user
