[gs-bugs] [Bug 690581] extensive output to stderr from pstoraster degrades printing performance

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon Jul 5 22:14:11 UTC 2010


http://bugs.ghostscript.com/show_bug.cgi?id=690581

--- Comment #4 from Hin-Tak Leung <hintak at ghostscript.com> 2010-07-05 22:14:08 UTC ---
(In reply to comment #3)
> The stderr output serves only for conveying status and error information to the
> log files of CUPS (error_log and page_log). For me logging also lokks
> exaggerated and it is really possible that the CUPS raster output device uses
> more CPU time on logging than on its actual work.
> 
> The "-dDEBUG" in pstoraster and pdftoraster are really not necessary.

My question was probably, what is the minimum debug stderr output needed, for
CUPS's status/error info tracking to still work correctly?

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list