[cups.general] Re: CUPS syslogging 2 lines every 5 seconds!

[Ming-Yang Yen]

"Michael Sweet" <mike at easysw.com> wrote in
message news:22918-cups.general at news.easysw.com...
> Sebastian Tennant wrote:
>> Hi all,
>>
>> I'm running a 2 week old installation of Debian Etch on an i686 platform
>> and
>> I've just noticed that my /var/log/cups/access_log is _huge_ (despite
>> daily
>> rotation) because the following two lines are being written every 5 secs:
>> ...
>> My printer's working OK, i.e., it prints fine from most applications
>> (Firefox
>> excepted).
>>
>> There can be no good reason for such endless repetition of information.
>> Anyone
>> know what's causing this and how I can stop it?
>
> This is GNOME constantly polling CUPS.  I don't know if it can be
> disabled, but I'd ask the GNOME folks for an answer...

I don't know about GNOME, whether you can make it stop doing that or not,
but you might be able to change the way cups logs things. Try editing your
cupsd.conf and find a variable that says LogLevel (or create it if it
donesn't exist) and make it "LogLevel none"

This is from the CUPS admin manual:

LogLevel

--------------------------------------------------------------------------------

Examples
LogLevel none
LogLevel emerg
LogLevel alert
LogLevel crit
LogLevel error
LogLevel warn
LogLevel notice
LogLevel info
LogLevel debug
LogLevel debug2

Description
The LogLevel directive specifies the level of logging for the ErrorLog file.
The following values are recognized (each level logs everything under the
preceding levels):

  a.. none - Log nothing.
  b.. emerg - Log emergency conditions that prevent the server from running.
  c.. alert - Log alerts that must be handled immediately.
  d.. crit - Log critical errors that don't prevent the server from running.
  e.. error - Log general errors.
  f.. warn - Log errors and warnings.
  g.. notice - Log temporary error conditions.
  h.. info - Log all requests and state changes (default).
  i.. debug - Log basic debugging information.
  j.. debug2 - Log all debugging information.

Hope that helps.