[X2Go-Commits] page changed: wiki:advanced:multi-node:x2goserver-printing

wiki-admin at x2go.org wiki-admin at x2go.org
Fri Mar 15 23:34:11 CET 2013


A page in your DokuWiki was added or changed. Here are the details:

Date        : 2013/03/15 22:34
Browser     : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address  : 46.142.171.115
Hostname    : 115-171-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:multi-node:x2goserver-printing?rev=1363365914
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:multi-node:x2goserver-printing
Edit Summary: 
User        : sunweaver

@@ -10,9 +10,9 @@
  
  ===== Using X2Go Printing on a Centralized CUPS Server =====
  
  <note>
- X2go Printing is intended for 
+ X2Go Printing is intended for 
     * use on low bandwith networks – like internet connections or GSM connections
     * 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.
  </note>
@@ -23,9 +23,9 @@
  If you
would like to run your X2Go server and the CUPS service on different machines (such a scenario is very common if you run more than one X2Go server on your network), you'll have to do things:
  
    - 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)
-   - 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.
   

  As first step: install the X2Go server printing add-on to your (every) X2Go server:
@@ -51,17 +51,17 @@
  <code>
  $ ssh-keygen -N "" -t dsa -f /root/.ssh/id_dsa-x2goprint
  </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>
  root at cupsserver:~$ ssh-copy-id /root.ssh/id_dsa-x2goprint x2goprint at x2goserver1.your.domain
  root at cupsserver:~$ ssh-copy-id /root.ssh/id_dsa-x2goprint x2goprint at x2goserver2.your.domain
  # etc.
  </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>
  root at cupsserver:~$ ssh -i  /root/.ssh/id_dsa-x2goprint x2goprint at x2goserver1.your.domain
  root at cupsserver:~$ ssh -i  /root/.ssh/id_dsa-x2goprint x2goprint at x2goserver2.your.domain



-- 
This mail was generated by DokuWiki at
http://wiki.x2go.org/




More information about the x2go-commits mailing list