openprinting / cups-sharing Goto Github PK

Dear CUPS Team,

I know that there is a quota system (https://openprinting.github.io/cups/doc/accounting.html), but I'm unable to figure out how to reset the quota. Could someone shed some light on this and update the documentation?

We have a really simple use case:

• set a limit for N pages on the P printer for the period of T seconds,
• after the T period, reset the quota -- set the same limit N for the same period T again.
• sometimes reset the quota during the T period

Is it possible with the current quota implementation? I tried setting the quota and period to 0, etc. but nothing works. After setting the limit again, I get the info that my quota has already exhausted -- which means that the previous limit is still in use.
And, are there any alive 3rd party quota solutions that you know of? I think that the pykota is EOL and I really can't find anything that is in wider use.

Kind regards,

--
Kamil

Hi, I just want to ask if it would be possible to add URL prefix for web interface configuration. Because it is impossible to host it under some domain e.g. my.domain.com/cups/. Workaround is to use subdomain :-/ e.g. cups.my.domain.com.

Note: The goal of this issue is to have a place to discuss the eventual removal of printer driver support and support for raw queues in OpenPrinting CUPS v3.0. The original Apple CUPS bug report has some additional history, and what exists here is an updated summary of that historical discussion.

Why do we want to do this?

• Raw queues used for special-use printers require custom applications that know about printer capabilities and how to produce printer-ready (document) data. Using CUPS is a convenience, but plenty of applications talk directly to printers (think Point of Sale systems)
• Raw queues used for shared printers require client software to talk directly to the server to get the printer capabilities, which breaks when sandboxing/AppArmor/SELinux is used
• Almost every printer manufactured since 2010 supports IPP/2.0 with standard file formats
  • Holdouts are industrial label printers and certain vertical market printers
• PPDs and drivers have been holding us back from offering better user experience (ready media, localization, full range of printer options/values), improved document processing, and improved accounting
• PPDs and drivers are a security and distribution nightmare

We already have a replacement for raw queues for shared printers (local/temporary queues managed by cupsd), and raw queues for special-use printers already largely bypass CUPS and can use existing commands or character device files to communicate with those printers.

As for printer drivers, those few printers that "need" them can migrate to standalone applications/services using the CUPS API to provide an IPP Everywhere-compatible Printer instance. PAPPL provides a convenient framework for easily creating these applications and porting existing CUPS raster drivers, and the following printer applications are already available or (in the case of Gutenprint) under development:

• hp-printer-app: PAPPL-based PCL printer application based on the CUPS rastertohp driver.
• LPrint: PAPPL-based label printer application, currently supporting Zebra and Dymo label printers with plans to support more, based on the CUPS rastertolabel driver. "Raw" printing is supported as well if you have an application that produces the native print data format.
• ps-printer-app: PAPPL-based PostScript printer application that supports all CUPS/PostScript printers via PPDs and includes all of the Foomatic and HPLIP drivers.
• Ghostscript Printer Application: PAPPL-based printer application for Ghostscript-based printer drivers.
• Gutenprint: A PAPPL-based printer application for all Gutenprint printer drivers.

A feature request: add per-task logs as text files and add ability to read them via web interface.

Currently the only way to get a per-task log is the following:
grep '\[Job XXX\]' /var/log/cups/error_log

What I would like:
a separate file like /var/log/cups/per-task-logs/printerName-jobID.log

Why?
I am using CUPS to build RPM packages: https://github.com/mikhailnov/pkg-builder-cups
(I do not know how this usecase will be covered after cups-backend becomes depreceated, but currently I did not find anything better than CUPS to be a simple scheduler for building RPM packages).
I want to have per-build logs and have access to them also via a web UI. Currently I see a full build log in /var/log/cups/error_log.

I understand that this use case does not match CUPS goals, but still openning this issue, may be it will be interesting for something else.