From 8d735931e2a93fab31d68772e8881faa6b030a10 Mon Sep 17 00:00:00 2001 From: Tomas Kuthan Date: Thu, 3 Apr 2014 17:58:43 +0200 Subject: Remove adb_policy_init and adb_policy_close Since f72c3ffa the policy is initialized as part of database. adb_policy_close is now a no-op, and adb_policy_init just makes sure the database is initialized. adb_policy_init is only called from kadm5_flush, and only if database initialization was successful beforehand, rendering this call redundant. Remove adb_policy_init and adb_policy_close and all their references in the code and documentation. --- doc/kadm5/api-funcspec.tex | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/kadm5/api-funcspec.tex b/doc/kadm5/api-funcspec.tex index bf885b464..c13090a51 100644 --- a/doc/kadm5/api-funcspec.tex +++ b/doc/kadm5/api-funcspec.tex @@ -1107,9 +1107,8 @@ the Admin API open. This function behaves differently when called by local and remote clients. For local clients, the function closes and reopens the Kerberos -database with krb5_db_fini() and krb5_db_init(), and closes and -reopens the Admin policy database with adb_policy_close() and -adb_policy_open(). Although it is unlikely, any other these functions +database with krb5_db_fini() and krb5_db_init(). +Although it is unlikely, either of these functions could return errors; in that case, this function calls kadm5_destroy and returns the error code. Therefore, if kadm5_flush does not return KADM5_OK, the connection to the -- cgit