[cups] debugging file auto-typing

Zdenek Dohnal zdohnal at redhat.com
Thu Feb 14 07:19:08 PST 2019


I would look into /var/spool/cups for files starting with 'd' and check
their file type. It will get you initial idea what filetype goes to CUPS.

Then the function, which does recognizing mime types, is mimeFileType()
from scheduler/type.c. I would recommend checking error_log with debug2
logging turned on or tracking the process with gdb.

On 2/14/19 2:03 AM, Tim Mooney wrote:
> All-
> Is there a recommended practice for debugging why CUPS chooses a certain
> mime type when auto-typing a print job?
> I know I can use local.types and my own types with priority() to force
> CUPS to prefer a particular type, but what I'm trying to determine is
> which types are coming out of the process as candidates.
> Is my best bet something like installing the debug symbols for
> 'cupsfilter' and stepping through what its doing with a debugger?
> If it makes a difference, this is for CUPS 1.4.2 on RHEL 6.10.  In
> addition, this is for a central CUPS print server that is receiving
> print jobs from a variety of client systems.
> Thanks,
> Tim

Zdenek Dohnal
Associate Software Engineer
Red Hat Czech - Brno TPB-C

More information about the cups mailing list