[FreeNX-kNX] how printing works

[ChrisB]

Antoine Martin <antoine at nagafix.co.uk> wrote on 30/09/2009 10:23:06:

> ChrisB wrote:
> > Antoine Martin <antoine at nagafix.co.uk> wrote on 29/09/2009 09:39:21:

> > It uses an ssh tunnel which redirects a port on the FreeNX server back 
to 
> > the workstation, so you can then connect to a port on the WS :631 or 
:445, 
> > via the redirected port.
> That's the easy part... with ssh -R

Hmmmm

> But how do you tell the client applications running on the server to
> talk to this particular cups server?

????

You tell KDE etc. which cupsd to talk to not the client applications . . .


> In a hosted environment there may be dozens of these cups servers
> running (one for each session)

Yup, one for each user printing through the tunnel.

> That's the bit I am missing...
> 
> If I only deal with the somewhat easier case of nix workstations with
> cupsd running on the client, why can't I just get the server to point
> the apps to talk directly to that remote cups server? (via ssh -R or
> plain tcp if on a secure LAN)


It's not an easier case if you have windows workstations not running 
cupsd, it's impossible. Given the large windows user base, it would be a 
fatal reduction in user base to not support them.

Most people want to spool to a queue on a local disk, then background the 
network transfer.

Cups deals with printer drivers, access rights etc locally.
In the olden days it was all lp to a remote IP, but then you had to 
manually set up printer options, trays paper size etc.


> And if so... how?
> (same question as above really)
> 

Try it !!

> > 
> >> Can anyone point me to some documentation?
> > 
> > 
> > No ! Did you not try Google.
> Yes.
> I never bother dozens of people on mailing lists without spending a fair
> amount of time doing my homework.
> Thanks for your very detailed response though!

That was not a detailed response !!!

You are now asking cups questions, for which there is slightly too much 
documentation !!

 
> > For a NIX workstation, you need to set up an ipp printer (typically) 
in 
> > cups on the server, pointing via the re-directed port to the 
workstation.
> I would like to avoid this part (as mentioned above).

Why, do you know anything easier ??

> If not, can this be done easily/reliably from a script? (and without

Yup.

> generating a whole new cupsd.conf if possible)

Nope.

One of the reasons for a userland cupsd is that the printing is only set 
up after the user has successfully logged in and their session has 
started.

If you didn't mind having all your users being printer administrators then 
you could just use the system cupds ( which of course you also use if you 
are NOT setting up remote printing ), because users could then set up and 
delete their own printers ( and everyone else's, and redirect everyone 
elses printing ) which in the real world, would not of course be 
considered rational behavior.

> 
> > For a windows WS you need an smb printer set up in cups on the server, 

> > which uses smbspool to connect via the redirected port to the print 
share 
> > on the workstation after the .ppd file has kicked off PS to Windows 
> > conversion.
> Sigh.

It ( nearly ) works. What's the problem ??






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090930/96858844/attachment.html>