Learn more about these different git repos.
Other Git URLs
If nscd is not installed, and in general we recommend not to use it, sss_useradd will show the following output:
# sss_useradd -u 999 -h /home/user999 -s /bin/bash user999 sh: /usr/sbin/nscd: No such file or directory sh: /usr/sbin/nscd: No such file or directory
but the user is created.
The tools try to flush the nscd cache by calling 'nscd -i ..' in a system() call. We should either test with stat() if nscd is available or suppress all output from the system() call. I would vote for stat() because the output in general might help the user.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 2.0
rhbz: => 0
blockedby: => blocking: => feature_milestone: => proposed_priority: => Optional
This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.
moving the ticket to needs_triage for discussion.
changelog: => design: => design_review: => 0 fedora_test_page: => mark: => 0 milestone: SSSD 2.0 => NEEDS_TRIAGE review: => 0 selected: => sensitive: => 0
The local provider is not actively developed anymore. When we upstream the work on the files provider, we either deprecate or remove the local provider completely.
In the meantime, I'm moving this ticket into "Patches welcome".
milestone: NEEDS_TRIAGE => SSSD Patches welcome
review: 0 => 1
Since the local provider is not being developed anymore, I'm closing this ticket as wontfix.
resolution: => wontfix status: new => closed
Metadata Update from @sbose: - Issue set to the milestone: SSSD Patches welcome
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/1889
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.