4 ms·
These would be metadata about completed print jobs. The PreserveJobHistory* options in cupsd.conf[0] control retention of this information; the default value is
by yrro 4y ago
These would be metadata about completed print jobs. The PreserveJobHistory* options in cupsd.conf[0] control retention of this information; the default value is 500, so most users who print occasionally will likely have entries going back a couple of years.
You can view (some) of it with: 'lpstat -W completed'; add '-l' for more detail. Add '-u USER' to view completed print jobs of another user (there doesn't seem to be any way to see _all_ user info, cups' command line tools always seem to have aggravating shortcomings like this...)
[0] https://www.cups.org/doc/man-cupsd.conf.html https://www.cups.org/doc/man-cupsd.conf.html
- Pinus 4y agoTo be clear: It was not just metadata, it was actual PDF:s — I tried opening several of them — named d<digits>-<digits>. But, as I said, after an OS update (to 11.7.1) (including a reboot, obviously), they were gone, and only metadata files (named c<digits>) remain.
- yrro 4y agoVery interesting. That certainly sounds like PreserveJobFiles was set to 'yes' or a stupidly high number. And it sounds like, as you say, a subsequent OS update changed it to a sensible setting. FYI the default value is 24 hours so it might be interesting for you to print something now, see if the job file (starting with d, I guess this is sort for 'document') is preserved after the print job completes, and then check a couple of days later to see if it's been removed by cups. [subsequent edit] Maybe you ran into https://github.com/apple/cups/issues/5747 https://github.com/apple/cups/issues/5747, "You really need to use a current release of CUPS. I suspect this is due to a known bug that was fixed a long time ago" - maybe that bug shipped with an older version of macOS and that explains what people are seeing.