This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
wiki:advanced:multi-node:x2goserver-printing [2011/06/07 23:19] sunweaver |
wiki:advanced:multi-node:x2goserver-printing [2016/09/23 09:41] (current) ionic Typo and headling capitalization fixes. |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Printing | + | ====== 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), then you will not need X2go printing. Configure your print server (mostly CUPS, Common Unix Printing | + | ===== Sites Where X2Go Printing |
- | ===== 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, |
- | :!: **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 |
- | > Please make sure that you have added the X2go repository | + | |
+ | Setting up CUPS and CUPS printers is not an explicit X2Go issue, please consult | ||
+ | |||
+ | ===== Using X2Go Printing on a Centralized CUPS Server ===== | ||
< | < | ||
- | X2go Printing is intended for | + | X2Go Printing is intended for |
- | * use on low bandwith | + | * use on low bandwidth |
- | * 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. | ||
</ | </ | ||
- | X2go Printing (i.e. the '' | + | :!: **Before you begin!** |
+ | > Please make sure that you are familiar with basic X2Go printing setups as described [[doc: | ||
- | For being able to use X2go printing, you'll need a running CUPS server. You can use your network' | + | If you would like to run your X2Go server |
- | By installing | + | - if running more than one X2Go server: setup up X2Go servers with [[wiki: |
+ | - 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 / | ||
+ | |||
+ | 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 '' | ||
+ | |||
+ | As first step: install the X2Go server printing add-on | ||
< | < | ||
- | $ aptitude install | + | $ sudo aptitude install |
</ | </ | ||
- | + | | |
- | After the installation, | + | Next, install |
- | + | ||
- | You may configure further options by editing the file “/ | + | |
< | < | ||
- | ## | + | $ sudo aptitude install |
- | ## | + | |
- | ## | + | |
- | + | ||
- | ## Server with x2go system | + | |
- | #x2goserver = local | + | |
- | + | ||
- | ## dsa key for user x2goprint | + | |
- | #printdsa = / | + | |
- | + | ||
- | ## command to generate pdf files | + | |
- | #ps2pdf = /usr/bin/gs -q -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile=" | + | |
</ | </ | ||
- | + | | |
- | + | On the CUPS server create | |
- | FIXME! The '' | + | |
< | < | ||
- | x2goprint ALL=(ALL) NOPASSWD: | + | $ mkdir -p /root/.ssh/ |
</ | </ | ||
- | ===== Using X2go Printing on a Centralized CUPS Server ===== | + | Now you can generate |
- | + | ||
- | If you would like to run your X2go server and the CUPS service on different machines, you'll need to generate | + | |
- | + | ||
- | Please make sure that you are logged in as user '' | + | |
< | < | ||
- | $ mkdir -p /root/.x2go/ssh/.x2goprint/ | + | $ ssh-keygen -N "" |
</ | </ | ||
- | Now you can generate | + | The public part of the key (''/ |
< | < | ||
- | $ ssh-keygen | + | root@cupsserver: |
+ | root@cupsserver: | ||
+ | # etc. | ||
</ | </ | ||
- | The public part of the key (''/ | + | 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 |
< | < | ||
- | x2goprint@x2goserver1:~$ cat id_dsa.pub >> ~/.ssh/authorized_keys | + | root@cupsserver:~$ ssh -i /root/.ssh/id_dsa-x2goprint |
- | x2goprint@x2goserver2:~$ cat id_dsa.pub >> ~/.ssh/authorized_keys | + | root@cupsserver:~$ ssh -i /root/.ssh/id_dsa-x2goprint x2goprint@x2goserver2.your.domain |
- | etc. | + | # etc. |
</ | </ | ||
- | Every X2go server that uses X2go printing needs to be known by the CUPS server. | + | If this is your first login from '' |
+ | |||
+ | |||
+ | At last, you have to add the following line to your /etc/sudoers | ||
< | < | ||
- | $ ssh -i / | + | x2goprint |
- | $ ssh -i | + | |
- | etc. | + | |
</ | </ | ||