You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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".
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/847
If nscd is not installed, and in general we recommend not to use it, sss_useradd will show the following output:
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.
Comments
Comment from dpal at 2011-04-14 15:01:58
Fields changed
milestone: NEEDS_TRIAGE => SSSD 2.0
Comment from dpal at 2012-01-19 03:14:50
Fields changed
rhbz: => 0
Comment from dpal at 2012-08-16 19:48:23
Fields changed
blockedby: =>
blocking: =>
feature_milestone: =>
proposed_priority: => Optional
Comment from dpal at 2012-09-04 23:25:05
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.
Comment from jhrozek at 2016-10-10 18:21:40
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
Comment from jhrozek at 2016-10-13 16:06:35
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
Comment from jhrozek at 2016-11-08 22:15:07
Fields changed
review: 0 => 1
Comment from jhrozek at 2016-11-25 09:35:33
Since the local provider is not being developed anymore, I'm closing this ticket as wontfix.
resolution: => wontfix
status: new => closed
Comment from sbose at 2017-02-24 14:53:38
Metadata Update from @sbose:
The text was updated successfully, but these errors were encountered: