Bug 28632 - Cleanup von Locks für Samba SID
Cleanup von Locks für Samba SID
Status: RESOLVED DUPLICATE of bug 41711
Product: UCS
Classification: Unclassified
Component: UMC - Users
UCS 3.0
Other Linux
: P4 enhancement (vote)
: UCS 3.x
Assigned To: UMC maintainers
:
Depends on: 27992
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-24 14:08 CEST by Arvid Requate
Modified: 2018-04-13 13:28 CEST (History)
6 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Cleanup, UCS Performance
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2012-09-24 14:08:48 CEST
Es sollte geprüft werden, wie sich die an Bug #27992 Comment 9 beobachteten Locks aufräumen lassen.

+++ This bug was initially created as a clone of Bug #27992 Comment 9 +++

Auch aufgefallen ist das jede Menge Locks für Samba SID zurückbleiben
  # udm settings/lock list | sed -ne 's/^DN: //p' | wc -l
  2002
Das Muster ist dabei immer ähnlich: Das Lock-Objekt wird angelegt, dann
freigegeben, und danach nochmals angelegt (und nicht mehr freigegeben).
Comment 1 Florian Best univentionstaff 2016-06-29 16:09:40 CEST
I guess this is a duplicate of Bug #41294 but I am really not sure.

*** This bug has been marked as a duplicate of bug 41294 ***
Comment 2 Florian Best univentionstaff 2016-06-29 17:30:42 CEST

*** This bug has been marked as a duplicate of bug 31414 ***
Comment 3 Florian Best univentionstaff 2017-07-08 13:34:47 CEST

*** This bug has been marked as a duplicate of bug 41711 ***