I have raised the default LogDebugHistory some years ago as most printing problems happen during the execution of a job and this way one gets a logging with debug verbosity only for jobs and standard verbosity for all the rest. This way one often did not need to ask the bug-reporting users to reproduce their problems after having set logging to debug mode but instead, one could simply start to work with the error_log auto-captured by Apport.
Up to now no one complained that it somehow overloaded system resources.
Please add a line "LogDebugHistory 200" to your /etc/cups/cupsd.conf and restart CUPS.
I will remove this change from the next release of the CUPS package.
OdyX, could you remove the LogDebugHistory=99999 default change from the CUPS package for Debian (remove log-debug-history-nearly-unlimited.patch)? Thanks.
I have raised the default LogDebugHistory some years ago as most printing problems happen during the execution of a job and this way one gets a logging with debug verbosity only for jobs and standard verbosity for all the rest. This way one often did not need to ask the bug-reporting users to reproduce their problems after having set logging to debug mode but instead, one could simply start to work with the error_log auto-captured by Apport.
Up to now no one complained that it somehow overloaded system resources.
Please add a line "LogDebugHistory 200" to your /etc/cups/ cupsd.conf and restart CUPS.
I will remove this change from the next release of the CUPS package.
OdyX, could you remove the LogDebugHistory =99999 default change from the CUPS package for Debian (remove log-debug- history- nearly- unlimited. patch)? Thanks.