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

Provide information about configuration options used #2051

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

Provide information about configuration options used #2051

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/1009

  • Created at 2011-09-26 16:27:16 by myllynen
  • Closed at 2020-03-24 14:22:04 as wontfix
  • Assigned to nobody

It might be worthwhile if sssd could provide info (perhaps when run with sufficiently high value of debug_level) about the configure options it was configured and compiled with. For example, whether SELinux support, libnl, and the kernel keyring support are available or not might be helpful information.

Comments


Comment from sgallagh at 2011-09-29 15:41:26

We'll accept patches, but we have no immediate plans to support this.

component: SSSD => Build Environment
milestone: NEEDS_TRIAGE => SSSD Deferred
priority: minor => trivial


Comment from dpal at 2012-01-19 03:22:37

Fields changed

rhbz: => 0


Comment from myllynen at 2017-02-24 14:31:41

Metadata Update from @myllynen:

  • Issue set to the milestone: SSSD Patches welcome

Comment from pbrezina at 2020-03-24 14:22:04

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.


Comment from pbrezina at 2020-03-24 14:22:05

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
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