Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LogLevel #4522

Closed
michaelrsweet opened this issue Nov 14, 2014 · 1 comment
Closed

LogLevel #4522

michaelrsweet opened this issue Nov 14, 2014 · 1 comment
Labels
duplicate This issue or pull request already exists question General usage question
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

Version: 2.0-current
CUPS.org User: paulkerry

Hi

[Kind of related to http://cups.org/str.php?L4507]

In the older versions of CUPS, for instance 1.4, the documentation for LogLevel in cupsd.conf had information as to what exactly would be logged, i.e.

http://cups.org/documentation.php/doc-1.4/ref-cupsd-conf.html#LogLevel
has "info - Log all requests and state changes"

but the documentation for 2.0
http://cups.org/documentation.php/doc-2.0/man-cupsd.conf.html
doesn't really specify what will and won't be logged using whichever LogLevel: it just says...
"Specifies the level of logging for the ErrorLog file. The value "none" stops all logging while "debug2" logs everything. The default is "warn".

I'm currently using "LogLevel info" and don't get very much information at all.
http://cups.org/str.php?L2458 has a very old example from a long time ago showing filters starting for instance that I no longer see.

Should everything still be logged as it was in earlier versions or should I now be expecting to see other things?

Many thanks
Paul.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Duping this to STR #4474 - please add your own comments there, but the plan is to try to normalize logging and be able to support filtering, etc. using the latest logging daemons. That will drive some standardization for logging in general...

@michaelrsweet michaelrsweet added P0 - Unassigned (New) duplicate This issue or pull request already exists question General usage question labels Mar 17, 2016
@michaelrsweet michaelrsweet added this to the Stable milestone Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists question General usage question
Projects
None yet
Development

No branches or pull requests

1 participant