[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#868728: cups requires do lpadmin configuration to share printers



On Tue 18 Jul 2017 at 18:44:55 -0400, Antoine Beaupré wrote:

> On 2017-07-18 23:17:10, Brian Potkin wrote:
> > On Tue 18 Jul 2017 at 14:43:19 -0400, Antoine Beaupré wrote:
> >
> >> On 2017-07-18 17:19:08, Brian Potkin wrote:
> >> 
> >> https://wiki.debian.org/PrintQueuesCUPS#Double_Filtering
> >> 
> >> Reading that section just makes me more confused - while I am sure I
> >> could spend the next 15 minutes trying to understand all the subtleties
> >> of the CUPS internals, I fail to see how users are expected to learn
> >> that stuff just to share printers over the network.
> >
> > Users are not sharing printers. You (and your server) are.
> 
> I don't get this. I am not a user?

Yes and no. From the point of view of the command 'lp -d ... job' issued
directly on the server you are the user. When the command is issued from
another machine on the network you (the administrator) are not a user.

When you (as administrator) advertise your printers you are said to
share them. Users use your shared printers - they do not cause them to
be shared. Your generosity is in serving up these printers.
 
> And I would argue this is not a "server": it's my workstation, to which
> a printer is connected. I just want to share that printer.

That makes your machine a server, Switch your machine off. How happy
will your users be? Argue your way out of the complaints you will get. :)

> >> I don't understand the trade-offs here: why isn't "raw" processing
> >> the default? What's the downside, if it allows automatic remote printing
> >> configurations?
> >
> > The problem appears to be you have a client which isn't doing raw
> > processing. Sort them out,
> 
> Is that normal behavior? Or is this a symptom of some (possible
> deliberate) misconfiguration on that client?

Just a normal misconfiguration. Tell them not to do double filtering.
It's evil and completely unnecessary.

-- 
Brian.


Reply to: