Hi All:
Making progress on printing using x2go on Vserver (with x2go server on one Vserver guest using postgresql backend and cups on another with ssh connection to x2go server).
Thanks for help (as always) Mike -
We can't, however, see the virtual x2go printer from the client connection to the x2go server when we try to print. May not matter, but if we loosen up settings in cupsd.conf on the cups server, we can connect from the x2go server via a browser and then can see the x2go printer (e.g., http://192.168.1.xx:631) and launch print jobs (i.e., by-passing x2goprint).
Q: we do not have cups installed on the x2go server - is that a mistake? Should the virutal x2go printer live on the x2go server, not the cups server? It wouldn't seem so...
So we think we're still missing something between x2goprint and cups.
Also, the "spool" link in the session is broken in .x2go in the user's home folder- does this matter? In the syslog of the x2go server we get:
Sep 29 11:39:40 vserver1 /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="/usr/bin/gnome-session" Sep 29 11:39:41 vserver1 /usr/bin/x2gomountdirs[9409]: WARNING: mounting of /home/user1/.x2go/S-user1-50-1348918777_stDGNOME_dp24/spool failed.
This error does not happen when we connect to a "regular" (non vserver guest) x2go server and print and the spool link is healthy".
Q: Does this matter? FYI - we were getting the same sort of error when we tried printing with cups and x2go server on the same Vserver guest (single node).
Vserver uses a "fstab" that sits outside of the "guest" environment that makes /tmp in the Vserver tmpf format and sets the size of /tmp, and the /etc/fstab inside the Vserver guest is blank. Would this cause the broken spool link?
Q: Our understanding is Vserver has some issues with "fuse" - is that something to look at?
Think/hope wer're getting close...thanks ,
Ted