Learn more about these different git repos.
Other Git URLs
This is causing a lot of confusion in the field. Running nscd with SSSD enabled is acceptable if it is used only for those maps that SSSD does not support (such as the host map). Additionally, it's fine to run it on the passwd, group and netgroup maps as long as it is recognized that this affects the predictability of the cache.
We should either remove this startup warning entirely or else rephrase it to be clear that if nscd is running, we recommend that it should be disabled for the maps handled by SSSD.
Better rephrase it to list only maps that SSSD supports.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.5.1
Not so fast.
Some libraries we use (libdbus) or may use in the future sometimes perform getpwnam()/getpwuid() calls on their own. When running w/o nscd this is ok because SSSD sets an environment variable that prevents sss_nss from recursing. When running with nscd instead it means that we may end up with a loop: SSSD -> NSCD -> SSSD and here we block.
If the passw/group maps are not cached by nscd it may work, as long as nscd does not do the lookups itself.
owner: somebody => sgallagh
status: new => assigned
Fixed by 50b2904
resolution: => fixed status: assigned => closed
rhbz: => 0
Metadata Update from @sgallagh: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.5.1
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1816
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.