[cups] CUPS overwrites printers.conf

[Helge Blischke]

> Am 23.05.2019 um 17:09 schrieb Robert Heller <heller at deepsoft.com>:
> 
> At Thu, 23 May 2019 15:30:00 +0200 "The CUPS user discussion list." <cups at cups.org <mailto:cups at cups.org>> wrote:
> 
>> 
>> Hello,
>> 
>> i am a little despairing. This is my printers.conf *i want to configure*:
>> 
>> ######################################START######################################
>> 
>> # Printer configuration file for CUPS v2.2.7
>> # Written by cupsd
>> # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
>> 
>> #Virtual Print-Queue
>> <Printer PC-Room-Printer>
>> UUID urn:uuid:bdaafacc-e917-312a-604b-1fda973daed1
>> Info Warteschlange Printer
>> Location Room
>> DeviceURI papercut:file:/dev/null
>> State Idle
>> StateTime 1558614195
>> ConfigTime 1545120668
>> Type 4
>> Accepting Yes
>> Shared Yes
>> JobSheets none none
>> QuotaPeriod 0
>> PageLimit 0
>> KLimit 0
>> OpPolicy default
>> ErrorPolicy retry-job
>> </Printer>
>> #RICOH1
>> <Printer ricohmpc4504ex01>
>> UUID urn:uuid:275b9c5f-9539-3830-5f6f-9a08b5098972
>> AuthInfoRequired none
>> Info Backend Printer
>> Location Room 3
>> DeviceURI papercut:ipps://<URL>:443/ipp/print
>> State Idle
>> StateTime 1558611662
>> ConfigTime 1553171061
>> Reason media-empty-warning
>> Type 4
>> Accepting Yes
>> Shared Yes
>> JobSheets none none
>> QuotaPeriod 0
>> PageLimit 0
>> KLimit 0
>> OpPolicy default
>> ErrorPolicy retry-job
>> </Printer>
>> #RICOH2
>> <Printer ricohmpc4504ex02>
>> UUID urn:uuid:b10d1c48-3a57-3a3b-40bf-56161ebbf0d7
>> AuthInfoRequired none
>> Info Backend Printer
>> Location Room 2
>> DeviceURI papercut:ipps://<URL>:443/ipp/print
>> State Idle
>> StateTime 1558614339
>> ConfigTime 1558610508
>> Reason media-empty-warning
>> Type 4
>> Accepting Yes
>> Shared Yes
>> JobSheets none none
>> QuotaPeriod 0
>> PageLimit 0
>> KLimit 0
>> OpPolicy default
>> ErrorPolicy retry-job
>> </Printer>
>> #RICOH3
>> <Printer ricohmpc4504ex03>
>> UUID urn:uuid:ff1b9efc-d965-31bb-5618-60704e8e7e64
>> AuthInfoRequired none
>> Info Backend Printer
>> Location Room 1
>> DeviceURI papercut:ipps://<URL>:443/ipp/print
>> State Idle
>> StateTime 1558614224
>> ConfigTime 1553181834
>> Reason media-empty-warning
>> Type 4
>> Accepting Yes
>> Shared Yes
>> JobSheets none none
>> QuotaPeriod 0
>> PageLimit 0
>> KLimit 0
>> OpPolicy default
>> ErrorPolicy retry-job
>> </Printer>
>> ######################################START######################################
>> 
>> I stop cups, modify printers.conf and start cups. After restart all is 
>> looking fine. Few moments later printers.conf and printers.conf.O were 
>> modified by cups with additional options. But this issue hits only 
>> <Printer ricohmpc4504ex02> and <Printer ricohmpc4504ex03>.
> 
> Are you running this under Ubuntu?  Is cups-browsed installed and running?  
> Are the ricoh printers network printers? If yes to all of that, what is 
> probably happening is that cups-browsed is using Avahi (Bonjour) to "helfully" 
> configure your printers for you.
> 
> I *always* uninstall cups-browsed. It is a pain in the ass and causes far more
> problems in an organized managed LAN. I guess it is fine for someone who is
> generally clueless and/or who "wanders" from LAN to LAN (eg a traveling
> laptop), but for a situation where there is a sys admin who has configured the
> printers just so (for whatever reason) an who does not what the reconfigured
> as per someone else's ideas, who might be trying to be helpful for a clueless
> end-user.
> 
>> 
>> Cups insert for example this directives to printer RICHO2 and RICHO3 
>> section:
>> 
>> Attribute marker-colors \#000000,#00FFFF,#FF00FF,#FFFF00,none
>> Attribute marker-levels 50,90,90,90,100
>> Attribute marker-low-levels 10,10,10,10,10
>> Attribute marker-high-levels 100,100,100,100,100
>> Attribute marker-names Black Toner,Cyan Toner,Magenta Toner,Yellow 
>> Toner,staples
>> Attribute marker-types toner,toner,toner,toner,staples
>> Attribute marker-change-time 1558614327
>> 
>> cups-waiting-for-job-completed  # "i dont want this option!
>> 
>> RICHO1 ist not affected, but is the same model.
>> 
>> I hope you can help.
>> 
>> Best regards
>> 
>> Micha
>> 

Instead of completely disabling cups-browsed, you may use the 
BrowseFilter
directive  in cups-browsed.conf to exclude these printers from being maintained by cups-browsed.

Helge