Open jacobmarble opened 8 years ago
Just a thought, beyond troubleshooting this feature may be useful as an audit method. We've had EDU sysadmins request the ability to match job data against the Google user who submitted the job. Simply logging the user along with job metadata like title may not be sufficient to match the user against the paper.
I'm dealing with a printer that tells CUPS "OK, job printed" but, in fact, no paper comes out. It would be helpful to retain the PDF job payload instead of deleting it, so that I can figure out what is unique about this PDF.
This should be a simple config option like
retain_job_payload
and should default to "do not retain".