-
Notifications
You must be signed in to change notification settings - Fork 252
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
KCM should handle its own configuration itself #6926
Labels
Comments
alexey-tikhonov
changed the title
KCM should use its own separate configuration storage (config_kcm.ldb)
KCM should handle its own configuration itself
Sep 13, 2023
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Sep 13, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926) Instead 'sssd_kcm' should take care of parsing/preparing configuration on its own (to be taken care of in separate PR).
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Sep 13, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926) Instead 'sssd_kcm' should take care of parsing/preparing configuration on its own (to be taken care of in separate PR).
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 21, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 21, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 22, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 27, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 27, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 27, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 27, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 28, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Sep 29, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Sep 29, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 2, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 6, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Oct 6, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Oct 6, 2023
KCM now uses the /var/lib/sss/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
aplopez
added a commit
to aplopez/sssd
that referenced
this issue
Oct 9, 2023
KCM now uses the ${SSS_STATEDIR}/db/config_kcm.ldb database to store its configuration. config.ldb is no longer used by KCM. The configuration text file remains the same. Resolves: SSSD#6926
Pushed PR: #6948 |
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 11, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 12, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 12, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 13, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 16, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Oct 16, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Nov 10, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Nov 14, 2023
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 3, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 3, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 4, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 7, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 17, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 19, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 29, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 30, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 30, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 30, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 31, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Jan 31, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 1, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 1, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 9, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 12, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 12, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 13, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 14, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 19, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 19, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 21, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 26, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Feb 29, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Mar 7, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
to alexey-tikhonov/sssd
that referenced
this issue
Mar 13, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see SSSD#6926)
alexey-tikhonov
added a commit
that referenced
this issue
Mar 18, 2024
The only usage was 'sssd-kcm.service', but it was wrong since 'sssd_kcm' should be usable without other SSSD packages being installed (see #6926) Reviewed-by: Justin Stephenson <[email protected]> Reviewed-by: Pavel Březina <[email protected]> Reviewed-by: Sumit Bose <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
KCM is currently using the shared config.ldb file to store its configuration. It should use a separate file so that it can be used independently of SSSD.
Replacing the ldb file is the simplest solution. It is also possible to keep the configuration in memory instead of an ldb file. Considering the file will not be shared with other daemon, there is no possibility of configuration mismatch between daemons.
The text was updated successfully, but these errors were encountered: