URL: https://github.com/SSSD/sssd/pull/106
Title: #106: Add a new "files" provider

pbrezina commented:
"""
> I hope this wouldn't be an issue because the inotify code doesn't call the 
> callbacks immediately but with a tevent timer (by default immediate tevent 
> action) which IIRC waits until the next 'tick' of the event loop and 
> therefore serializes the callbacks.

Hmm, we actually don't need the request at all since the update is synchronous:
```
inotify:
    run callback
pwupdate: 
    update := true
    update()
    update := false
    finish request(ctx->request)
```
Therefore all `D-Bus` messages that comes during cache update are queued until 
the update is finished and only then are messages read from the bus and 
processed. Thus having ctx->request non null should not be posssible.

However, there should be two update states and two requests -- one for users 
(DP_USER) and one for groups (DP_GROUP) to stay completely clean and safe.
"""

See the full comment at 
https://github.com/SSSD/sssd/pull/106#issuecomment-279674481
_______________________________________________
sssd-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to