Bug 44147 - cups-printers listener needlessly reloads samba on all printservers for each change
cups-printers listener needlessly reloads samba on all printservers for each ...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Printserver
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-30 12:25 CEST by Arvid Requate
Modified: 2020-07-03 20:55 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.034
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:
requate: Patch_Available+


Attachments
avoid_reloading_samba_on_unaffected_servers.patch (2.21 KB, patch)
2017-03-30 12:25 CEST, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-03-30 12:25:25 CEST
Created attachment 8690 [details]
avoid_reloading_samba_on_unaffected_servers.patch

When a printer share is created, updated or deleted, the cups-printers listener reloads samba on *all* printservers, also on unaffected ones.

The attached patch might be suitable to fix this. I guess I have been to shy with my changes for Bug #36578 at that time.
Comment 1 Arvid Requate univentionstaff 2017-03-30 12:28:37 CEST
When fixing this, please also check

* services/univention-samba4/samba-shares.py
* services/univention-samba/samba-shares.py

AFAICS they do this as well.
Comment 2 Stefan Gohmann univentionstaff 2017-04-18 07:57:03 CEST
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:55:14 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.