Bug 1763161

Summary: High load in systemd when cups.path and cups.service is enabled
Product: Red Hat Enterprise Linux 8 Reporter: David Tardon <dtardon>
Component: systemdAssignee: Michal Sekletar <msekleta>
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: msekleta, systemd-maint-list
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-239-19.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:45:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Tardon 2019-10-18 11:28:10 UTC
This bug was initially created as a copy of Bug #1641777

I am copying this bug because: 
It's still a bug in 8.x.


Description of problem:
When I send many jobs for printing, then the machine experiences high load caused by systemd process. This behavior happens when cups.service and cups.path are both enabled and running.

Version-Release number of selected component (if applicable):
systemd-219-57.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
Scripts and steps how to reproduce are in https://bugzilla.redhat.com/show_bug.cgi?id=1589388

Actual results:
High load of systemd process

Expected results:
No high load

Additional info:
This issue is actually clone of https://bugzilla.redhat.com/show_bug.cgi?id=1589388 , which is reported on CUPS component. After talking with Michal Sekletar he proposed to create separate bug for investigating, if it is really systemd issue or only cups issue.

Comment 1 Michal Sekletar 2019-10-20 15:12:46 UTC
https://github.com/systemd-rhel/rhel-8/pull/29

Comment 3 Lukáš Nykrýn 2019-10-22 14:02:10 UTC
fix merged to github master branch -> https://github.com/systemd-rhel/rhel-8/pull/29 -> post

Comment 7 errata-xmlrpc 2020-04-28 16:45:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1794