On 05/18/2010 06:47 AM, Sumit Bose wrote:
ok, resetting all the resolver data is not a good idea. Please find
attached a new series of patches which tries to only do what is really
needed:
0001-Revert-Create-kdcinfo-and-kpasswdinfo-file-at-startu.patch
Ack
0002-Refactor-data-provider-callbacks.patch
Ack
0003-Add-offline-callbacks.patch
Ack
0004-Refactor-krb5_finalize.patch
Ack
0005-Add-run_callbacks-flag.patch
This new patch adds a flag and a function to set it to request that
the callbacks are run the next time the resolver is called.
Ack
0006-Add-callback-to-remove-krb5-info-files-when-going-of.patch
This patch new set the run_callbacks flag only for the KDC and if
available for the kpasswd service.
Ack
0007-Krb5-locator-plugin-returns-KRB5_PLUGIN_NO_HANDLE.patch
Ack
0008-Refactor-krb5-SIGTERM-handler-installation.patch
Ack
0009-Add-krb5-SIGTERM-handler-to-ipa-auth-provider.patch
Ack
0010-Add-offline-callback-to-disconnect-global-SDAP-handl.patch
This new patch adds an offline callback to the LDAP/IPA id provider
which set the connected flag of the global SDAP handle to false.
Otherwise this connection will still be used if the transition to
the offline state was triggered by SIGUSR1 or an other provider.
Ack
I tested these patches against a FreeIPA v2 server (sssd using the IPA
backend)
--
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/