Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable ifp responder by default #3393

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

enable ifp responder by default #3393

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2351

  • Created at 2014-06-04 11:14:53 by pbrezina
  • Closed as Invalid
  • Assigned to nobody

Tools that are or will be using our D-Bus interface will not work if the IFP responder is not running. We should make the responder enabled by default with the possibility to disable it if not needed.

Comments


Comment from dpal at 2014-07-03 16:00:29

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => todo


Comment from dpal at 2014-09-26 18:49:59

Fields changed

mark: => 0


Comment from jhrozek at 2015-02-10 14:35:47

It's already socket activated, I propose close/wontfix.

priority: major => trivial


Comment from jhrozek at 2015-02-10 17:29:28

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog


Comment from jhrozek at 2015-02-12 20:36:32

Mass-moving tickets not planned for any immediate release and re-setting priority.

milestone: SSSD 1.13 backlog => SSSD Deferred
priority: trivial => major


Comment from jhrozek at 2016-11-10 22:54:19

I think we should close this one and instead implement ticket #3129.

review: 0 => 1
sensitive: => 0


Comment from jhrozek at 2016-11-25 09:50:02

We alrady have a PR to socket-activate IFP.

resolution: => wontfix
status: new => closed


Comment from pbrezina at 2017-02-24 14:57:56

Metadata Update from @pbrezina:

  • Issue set to the milestone: SSSD Patches welcome
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant