Bug 50853 - CUPS shall use syslog
CUPS shall use syslog
Status: NEW
Product: UCS
Classification: Unclassified
Component: Printserver
UCS 4.4
Other Linux
: P5 normal (vote)
: UCS 5.0-0-errata
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-02-26 09:30 CET by Nico Gulden
Modified: 2021-04-28 10:17 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Gulden univentionstaff 2020-02-26 09:30:39 CET
Currently CUPS uses it's default logfiles for logging. This results in CUPS Server restarts during log rotation.

Restarting the CUPS server results in loosing unfinished print jobs, when CUPS is used together with PaperCut. See https://www.papercut.com/kb/Main/LosingHeldJobsCUPS

Changing log rotation behavior would eliminate one cause of CUPS server restarts. To achieve this, CUPS could be configured to use syslog as log target with it's access and error log. See https://www.cups.org/doc/man-cups-files.conf.html