Bug 1196218

Summary: Global "ErrorPolicy" option does not get validate by cups
Product: Red Hat Enterprise Linux 7 Reporter: Rupesh Patel <rupatel>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact: Jana Heves <jsvarova>
Priority: medium    
Version: 7.1CC: jscotka, psklenar, qe-baseos-daemons, twaugh
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: cups-1.6.3-19.el7 Doc Type: Bug Fix
Doc Text:
The ErrorPolicy directive is now validated The ErrorPolicy configuration directive was not validated on startup, and an unintended default error policy could be used without a warning. The directive is now validated on startup and reset to the default if the configured value is incorrect. The intended policy is used, or a warning message is logged.
Story Points: ---
Clone Of: 1196217 Environment:
Last Closed: 2015-11-19 12:10:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1205796, 1251102    

Description Rupesh Patel 2015-02-25 14:06:46 UTC
+++ This bug was initially created as a clone of Bug #1196217 +++

Version - cups-1.4* and above 

If i modify any of the option in cups.conf  and make spell mistake, it complains in error_log. However, this doesn't seems to validating option "ErrorPolicy" we added sometime back (default releases in RH-6 and after 1.3.7 rebase in RH-5)

Steps to reproduce this... 

1)
[root@dhcp233-34 ~]# grep Max /etc/cups/cupsd.conf
MaxLogSize   <---------- Remove size
[root@dhcp233-34 ~]#

[root@dhcp233-34 ~]# /etc/init.d/cups restart
Stopping cups:                                             [  OK  ]
Starting cups:
[root@dhcp233-34 ~]#                                        [  OK  ]
[root@dhcp233-34 ~]# cat /var/log/cups/error_log
E [25/Feb/2015:18:10:59 +0530] Missing integer value for MaxLogSize on line 1! <------ Complains integer missing

2)

[root@dhcp233-34 ~]# grep LogLevel  /etc/cups/cupsd.conf
LogLevel rn <------- made spell mistake in LogLevel
[root@dhcp233-34 ~]#

[root@dhcp233-34 ~]# cat /var/log/cups/error_log
E [25/Feb/2015:18:10:59 +0530] Missing integer value for MaxLogSize on line 1!
W [25/Feb/2015:18:11:57 +0530] Unknown LogLevel rn on line 11. <---------------  Complain for unknown level
[root@dhcp233-34 ~]#

[root@dhcp233-34 ~]# grep Error  /etc/cups/cupsd.conf
ErrorPolicy test <----------Error policy is invalid but it doesn't complain anything.
[root@dhcp233-34 ~]#

[root@dhcp233-34 ~]# cat /var/log/cups/error_log
E [25/Feb/2015:18:10:59 +0530] Missing integer value for MaxLogSize on line 1!
W [25/Feb/2015:18:11:57 +0530] Unknown LogLevel rn on line 11.
[root@dhcp233-34 ~]#

 ^^ no such commented by cups in error_log for invalid entry.

Comment 3 errata-xmlrpc 2015-11-19 12:10:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2386.html