Differences

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

--- wiki:advanced:multi-node:x2goserver-printing [2011/11/08 11:58]
sunweaver wiki:installing_x2go_printing_debian_ubuntu renamed to wiki:advanced:multi-node:x2goserver-printing (Namespace cleanup)
+++ wiki:advanced:multi-node:x2goserver-printing [2013/03/15 22:34]
sunweaver
@@ Line 1: / Line 1: @@
-====== Printing and X2go ======
+====== Printing Revisited ======
-If all your X2go servers, X2go clients and the available network printers are all on the same site (i.e. in the same office), then you will not need X2go printing. Configure your print server (mostly CUPS, Common Unix Printing System) to print directly to your office printers. Also make sure that your office printers are available to user's that logon to your X2go server (setting up CUPS printers is not an issue of X2go, please consult the CUPS howtos available on the internet).
+===== Sites where X2Go Printing does not Make Sense =====
-===== Installing 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.
-:!: **Before you begin!**
+Connect all your office printers directly to the network (IPP, LPD, AppJetDirect printing). Configure your central print server (mostly CUPS, Common Unix Printing System) to print directly to your networked office printers. Also make sure that your office printers are available to users that logon to your X2Go server(s).
-> Please make sure that you have added the X2go repository to your package management system. The required steps are described here: [[adding the x2go repository (Debian)|Debian]], [[adding the x2go repository (Ubuntu)|Ubuntu]] (depending on the distro that you have chosen for your X2go server).
+Setting up CUPS and CUPS printers is not an explicit X2Go issue, please consult the CUPS howtos available on the internet.
+===== 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
+   * 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>
-X2go Printing falls into two components:
+:!: **Before you begin!**
+> Please make sure that you are familiar with basic X2Go printing setups as described [[doc:installation:printing|here]]. Only if you have successfully set up a single-node printing X2Go site go deeper and try out the multi-node setup.
-  * cups-x2go -- a CUPS backend that spools X2go print jobs
+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:
-  * x2goprint -- the X2go server-side printing component that accepts cups-x2go print jobs and processes them towards connected X2go clients
-X2go server-side printing component (i.e. the ''x2goprint'' command) has become a standard component of the ''x2goserver'' package (since May 2011). Before that time it used to be an extra package.
+  - 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)
-For being able to use X2go printing, you'll need a running CUPS server. You can use your network's existing CUPS server or you can install a CUPS server on the same machine as the X2go server tools are running on.
+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.
-The minimal X2go server + CUPS setup is: install x2goserver, cups, cups-x2go on the same machine. Printing should work out of the box. For local X2go printing (local means here: all processes take place on the same machine) no further system setup is needed.
+As first step: install the X2Go server printing add-on to your (every) X2Go server:
-<note>Before Sep 2011 configuring sudo was needed for local X2go printing, since then setting up sudo is only needed if CUPS with cups-x2go and the X2go server package are installed on //different// machines.</note>
-By installing the X2go CUPS engine (package: ''cups-x2go'') you add a »Virtual X2go Printer« backend to your CUPS server:
 <code>
-$ aptitude install cups-x2go
+$ sudo aptitude install x2goserver-printing
 </code>
-After the installation, you are able to add a new printer in CUPS, possibly named: »x2goprinter« (name is arbitrary). As printing device (i.e. backend) you should select the “Virtual X2go Printer” (vendor: »generic«, model: »Generic CUPS-X2GO Printer«).
+Next, install the CUPS X2Go backend on the CUPS server:
-You may configure further options by editing the file “/etc/cups/cups-x2go.conf” (the below code block shows the default set of options):
 <code>
-##
+$ sudo aptitude install cups-x2go
-##  cups-x2go.conf -- CUPS Backend Configuration
-##
-## Server with x2go system
-#x2goserver = local
-## dsa key for user x2goprint
-#printdsa = /root/.x2go/ssh/.x2goprint/id_dsa
-## command to generate pdf files
-#ps2pdf = /usr/bin/gs -q -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile="%s.pdf" -dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/prepress -c .setpdfwrite -f "%s"
-## loglevel for cups-x2go, possible values: emerg, alert, crit, err, warn, notice, info, debug
-#loglevel = notice
 </code>
-===== Using X2go Printing on a Centralized CUPS Server =====
-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 servers on your network), you'll have to do things:
-  - generate a pair of SSH keys to faciliate communication between those two machines
-  -  add a line to the /etc/sudoers file on every X2go server that shall be able to accept print jobs from the central CUPS server
-Please make sure that you are logged in as user ''root'' on the system running the CUPS service and add the following folders:
+On the CUPS server create ''root'''s SSH configuration directory:
 <code>
 $ mkdir -p /root/.ssh/
 </code>
-Now you can generate the keys (on each X2go server that shall have access to the CUPS service):
+Now you can generate an SSH public/private key. This key is used to allow passwordless logons from ''root@cupsserver'' to ''x2goprint@x2goserverX''.
 <code>
@@ Line 74: / Line 53: @@
 </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@cupsserver:~$ ssh-copy-id /root.ssh/id_dsa-x2goprint x2goprint@x2goserver1
+root@cupsserver:~$ ssh-copy-id /root.ssh/id_dsa-x2goprint x2goprint@x2goserver1.your.domain
-root@cupsserver:~$ ssh-copy-id /root.ssh/id_dsa-x2goprint x2goprint@x2goserver2
+root@cupsserver:~$ ssh-copy-id /root.ssh/id_dsa-x2goprint x2goprint@x2goserver2.your.domain
-etc.
+# 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@cupsserver:~$ ssh -i  /root/.ssh/id_dsa-x2goprint x2goprint@x2goserver1
+root@cupsserver:~$ ssh -i  /root/.ssh/id_dsa-x2goprint x2goprint@x2goserver1.your.domain
-root@cupsserver:~$ ssh -i  /root/.ssh/id_dsa-x2goprint x2goprint@x2goserver2
+root@cupsserver:~$ ssh -i  /root/.ssh/id_dsa-x2goprint x2goprint@x2goserver2.your.domain
-etc.
+# etc.
 </code>
+If this is your first login from ''root@x2goserverX.your.domain'' to ''x2goprint@x2goserverX.your.domain'' the SSH command will ask you to accept the host key of the X2Go server(s). Please accept the displayed host keys.
 At last, you have to add the following line to your /etc/sudoers file. Normally the command ''visudo'' is highly recommended for editing the sudoers file, as it performs sanity checks on the sudoers file and reports if you made a mistake while editing the file.

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools