User Tools

Site Tools


wiki:advanced:multi-node:x2goserver-printing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:advanced:multi-node:x2goserver-printing [2013/03/15 16:45]
sunweaver
wiki:advanced:multi-node:x2goserver-printing [2016/09/23 09:41] (current)
ionic Typo and headling capitalization fixes.
Line 1: Line 1:
 ====== Printing Revisited ====== ====== Printing Revisited ======
  
-===== Sites where X2Go Printing ​does not Make Sense =====+===== Sites Where X2Go Printing ​Does Not Make Sense =====
  
 If all your X2Go servers, X2Go clients and the available network printers are all on the same site (i.e. in the same office) and you neither intend to provide mobile or home office desktop environments,​ then you will __not__ need X2Go printing. ​ If all your X2Go servers, X2Go clients and the available network printers are all on the same site (i.e. in the same office) and you neither intend to provide mobile or home office desktop environments,​ then you will __not__ need X2Go printing. ​
Line 12: Line 12:
  
 <​note>​ <​note>​
-X2go Printing is intended for  +X2Go Printing is intended for  
-   * use on low bandwith ​networks – like internet connections or GSM connections+   * use on low bandwidth ​networks – like internet connections or GSM connections
    * use of printers that are directly connected to X2Go (thin-)clients    * use of printers that are directly connected to X2Go (thin-)clients
 For other scenarios, please use a central CUPS server (see multi-node printing below) without the X2Go printing feature installed. For other scenarios, please use a central CUPS server (see multi-node printing below) without the X2Go printing feature installed.
Line 24: Line 24:
  
   - if running more than one X2Go server: setup up X2Go servers with [[wiki:​advanced:​multi-node:​x2goserver-pgsql|PostgreSQL as X2Go session database backend]]   - if running more than one X2Go server: setup up X2Go servers with [[wiki:​advanced:​multi-node:​x2goserver-pgsql|PostgreSQL as X2Go session database backend]]
-  - generate a pair of SSH keys on the CUPS server to faciliate ​communication between CUPS server and X2Go server(s) +  - generate a pair of SSH keys on the CUPS server to facilitate ​communication between CUPS server and X2Go server(s) 
-  - add a line to the /​etc/​sudoers file on every X2go server that enables the X2Go Server (script: ''​x2goprint''​) to accept print jobs from the central CUPS server (pushed there via SCP)+  - add a line to the /​etc/​sudoers file on every X2Go server that enables the X2Go Server (script: ''​x2goprint''​) to accept print jobs from the central CUPS server (pushed there via SCP)
  
 Please make sure that you are logged as a user on CUPS and X2Go server(s) that can become the super-user by running the ''​sudo''​ command. Please make sure that you are logged as a user on CUPS and X2Go server(s) that can become the super-user by running the ''​sudo''​ command.
Line 53: Line 53:
 </​code>​ </​code>​
  
-The public part of the key (''/​root/​.ssh/​id_dsa-x2goprint.pub''​) needs to be added to the ''​x2goprint''​ user's ''​authorized_keys''​ file on each of your X2go servers. You can use the ''​ssh-copy-id''​ command for that:+The public part of the key (''/​root/​.ssh/​id_dsa-x2goprint.pub''​) needs to be added to the ''​x2goprint''​ user's ''​authorized_keys''​ file on each of your X2Go servers. You can use the ''​ssh-copy-id''​ command for that:
  
 <​code>​ <​code>​
Line 61: Line 61:
 </​code>​ </​code>​
  
-Every X2Go server that uses X2Go printing needs to be known by the CUPS server. Regarding your name resolution type, you'll need to add the host names for example to the local /etc/hosts file (your even better: use your local DNS server!!!). Please test if you are able to build up SSH connections from your CUPS server to your X2go servers by entering the following command.+Every X2Go server that uses X2Go printing needs to be known by the CUPS server. Regarding your name resolution type, you'll need to add the host names for example to the local /etc/hosts file (your even better: use your local DNS server!!!). Please test if you are able to build up SSH connections from your CUPS server to your X2Go servers by entering the following command.
  
 <​code>​ <​code>​
wiki/advanced/multi-node/x2goserver-printing.1363365914.txt.gz · Last modified: 2013/03/15 16:45 by sunweaver