[cups.general] Precedence of OpPolicy in Class and Printer

[Michael Sweet]

Vince,

If a job is submitted to a class, the class's policy is used.

If a job is submitted to a printer, the printer's policy is used.

If there is no named policy in the class or printer definition, then the default policy applies.

Operation policies can be shared between multiple printers/classes.

Each policy is self-contained - there is no inheritance (although there is a bug for that...) and if a class and the printers it contains have different policies, you can end up with some interesting behaviors...


On May 30, 2012, at 10:21 PM, Vince McIntyre wrote:

> Hi,
> 
> I would like to define some classes and apply different OpPolicy settings to them.
> 
> I notice that both <Class> and <Printer> can take an OpPolicy directive but I can't figure out from the documentation which would take precedence.
> The usual usage of these printers is people print to the specific printer queue
> rather than a class queue.
> 
> If the <Class> has an OpPolicy 'foo' but the <Printer> does not have an explicit OpPolicy directive, what does the policy end up being - 'foo' or 'default'? I'm expecting the Printer inherits from the Class.
> 
> What happens if a printer (again no OpPolicy) is in _two_ classes?
> Mm. Maybe there's no inheritance?
> 
> The subtext here is that I would like to be able to set/modify OpPolicy for a heap of printers at once instead of each individually. But I'm still expecting users to print to individual printers.
> 
> version: cups 1.4.4 (debian 6/squeeze)
> 
> kind regards
> _______________________________________________
> cups mailing list
> cups at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair