Bug 1511945 - Support notification mechanism for KCM caches
Summary: Support notification mechanism for KCM caches
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: sssd
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Hrozek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1508945
TreeView+ depends on / blocked
 
Reported: 2017-11-10 13:29 UTC by Debarshi Ray
Modified: 2020-05-02 18:50 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-11 15:04:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4592 0 None open Support notification mechanism for KCM caches 2020-10-20 18:22:18 UTC

Description Debarshi Ray 2017-11-10 13:29:48 UTC
Since the KCM caches are implemented by a D-Bus service, it would be good to have a signal that's emitted whenever the caches change. It would be analogous to using inotity watches for FILE or DIR caches.

The lack of a notification API means gnome-online-accounts has to poll the cache every few seconds to keep the GNOME integration in sync. Polling is problematic because it hurts battery consumption. This has already been a problem with KEYRING caches. I hope KCM will make things better.

Comment 1 Debarshi Ray 2017-11-10 13:33:51 UTC
Upstream bug: https://pagure.io/SSSD/sssd/issue/3568

Comment 2 Lukas Slebodnik 2017-11-10 17:41:37 UTC
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3568

Comment 3 Fedora End Of Life 2018-02-20 15:29:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 4 Fabiano Fidêncio 2018-04-11 15:04:00 UTC
This is an RFE that's going to be tracked upstream by https://pagure.io/SSSD/sssd/issue/3568 (as mentioned in comment 2).

I'm closing this bug as "UPSTREAM" and we'll track its progress in the pagure issue.

Please, feel free to re-open the bug in case you think that's not the best approach to take.


Note You need to log in before you can comment on or make changes to this bug.