[cups.bugs] [LOW] STR #2309: LogLevels "info" and "warn" do not work as expected

[Kurt Pfeifle]

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

I may have found a little bug in...

   ...either how CUPS handles its versious LogLevel settings,
   ...or in my understanding of these functions

I wrote a simple backend in Bash, that throws away the job, and just tests
the CUPS logging. Here is what the code does:

  echo 1>&2
  echo "EMERG:  This is a \"emergency\" level log message (echoed to
stderr)" 1>&2
  echo "ALERT:  This is a \"alert\" level log message (echoed to stderr)" 
   1>&2
  echo "CRIT:   This is a \"critical\" level log message (echoed to
stderr)"  1>&2
  echo "ERROR:  This is a \"error\" level log message (echoed to stderr)" 
   1>&2
  echo "WARN:   This is a \"warn\" level log message (implemented??)
(echoed to stderr)"  1>&2
  echo "WARN    This is a modified \"warn\" level log message
(implemented??) (echoed to stderr)"  1>&2
  echo "WARN:   This is another modified \"warn\" level log message
(implemented??) (echoed to stdout)
  echo "NOTICE: This is a \"notice\" level log message (echoed to stderr)"
   1>&2
  echo "INFO:   This is a \"info\" level log message (echoed to stderr)"  
   1>&2
  echo "INFO    This is a modified \"info\" level log message (echoed to
stderr)"  1>&2
  echo "INFO:   This is another modified \"info\" level log message
(echoed to stdout)"
  echo "INFO:   This is a 2nd \"info\" level log message (echoed to
stderr)"  1>&2
  echo "INFO:   This is a 3rd \"info\" level log message (echoed to
stderr)"  1>&2
  echo "DEBUG:  This is a \"debug\" level log message (echoed to stderr)" 
   1>&2
  echo "DEBUG2: This is a \"debug2\" level log message (echoed to stderr)"
   1>&2
  echo 1>&2

When I set LogLevel info" and I get this in the error_log:

  I [25/Mar/2007:05:38:47 +0100] Adding start banner page "none" to job
207.
  I [25/Mar/2007:05:38:47 +0100] Adding end banner page "none" to job 207.
  I [25/Mar/2007:05:38:47 +0100] Job 207 queued on "4logtesting" by
"kpfeifle".
  I [25/Mar/2007:05:38:47 +0100] Started filter
/usr/lib/cups/filter/pstops (PID 7901) for job 207.
  I [25/Mar/2007:05:38:47 +0100] Started backend
/usr/lib/cups/backend/4logtesting (PID 7902) for job 207.
  X [25/Mar/2007:05:38:47 +0100] [Job 207] This is a "emergency" level log
message (echoed to stderr)
  A [25/Mar/2007:05:38:47 +0100] [Job 207] This is a "alert" level log
message (echoed to stderr)
  C [25/Mar/2007:05:38:47 +0100] [Job 207] This is a "critical" level log
message (echoed to stderr)
  E [25/Mar/2007:05:38:47 +0100] [Job 207] This is a "error" level log
message (echoed to stderr)
  N [25/Mar/2007:05:38:47 +0100] [Job 207] This is a "notice" level log
message (echoed to stderr)

Why are neither INFO nor WARN messages appearing? Where is the bug? (I
assume the hierarchy of LogLevels goes like this: none emerg alert crit
error warn notice info debug debug2. - Is that right?)

(I've only tested current SVN trunk -- not sure what the result in
branches would be...)

Link: http://www.cups.org/str.php?L2309
Version: 1.3-current