[cups.development] [RFE] STR #2458: Move backend exit status report to 'LogLevel info' (even if successful)

[Kurt Pfeifle]

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

[STR New]

The error_log in 'LogLevel info' should be a *little* bit more verbose.
Specifically, I'd like to see at least *one* additional line that
indicates once the job has been send off the backend successfully (if the
filtering chain or the backend fails, it does log an error already).

Here is an example of the current error_log in 'LogLevel debug'

-------------------- snip --------------------------------------------
I [25/Jul/2007:19:48:35 +0200] Adding start banner page "none" to job
149611.
I [25/Jul/2007:19:48:35 +0200] Adding end banner page "none" to job
149611.
I [25/Jul/2007:19:48:35 +0200] Job 149611 queued on "SCHP070" by
"BOS_ALL\hgurwell".
I [25/Jul/2007:19:48:35 +0200] Started filter /usr/lib/cups/filter/pstops
(PID 17595) for job 149611.
I [25/Jul/2007:19:48:35 +0200] Started filter
/usr/lib/cups/filter/foomatic-rip (PID 17596) for job 149611.
I [25/Jul/2007:19:48:35 +0200] Started backend
/usr/lib/cups/backend/socket (PID 17597) for job 149611.
-------------------- snip --------------------------------------------

This (default) log level gives us 7 lines per job.

My above suggestion would add another one. I think it is essential to log
success of the backend for newbie users in cases where later the printer
fails -- newbies often do not increase the log level, but *may* look into
the error_log....

Here are 2 more lines I'd like to see in 'LogLevel info':

 * the line reporting the "auto-typing" result.
 * a summary line that reports argv[0] - argv[6]

This would give a total of 10 lines per job, and a more complete picture
about each print job even in this log level.

Link: http://www.cups.org/str.php?L2458
Version:  -feature