https://bugzilla.novell.com/show_bug.cgi?id=744301
https://bugzilla.novell.com/show_bug.cgi?id=744301#c9
--- Comment #9 from Johannes Meixner 2012-02-01 15:54:31 UTC ---
FYI,
regarding having "LogLevel debug" by default in comment #6:
Pros:
When users like to report a printing issue, they must
"Usually provide CUPS debug messages" as described at
http://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue
The manual "LogLevel debug" setting is annoying.
To get better printing issue reports it would help
to have "LogLevel debug" by default.
In this case even the YaST printer setup
would show by default more meaningful
"CUPS log information while processing the testpage"
if the user clicked "Testpage printing failed".
Having "LogLevel debug" by default would not fill up the disk
because the default "MaxLogSize" is 1MB and once a log file
exceeds the maximum size it is closed and renamed to filename.O
to that there are at most two log files (filename and filename.O)
with maximum size 1MB.
Cons:
The counter-argument is security.
With "LogLevel debug" by default sensitive information may be
stored in /var/log/cups/error_log
see the "Possibly insecure default LogFilePerm value 0644" mails
on cups@easysw.com in particular Michael Sweet's reply:
http://www.cups.org/newsgroups.php?s1+gcups.general+v6+T+Q%22Possibly+insecu...
and bug #704154
I.e. "LogLevel debug" by default would re-open bug #704154
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.