Skip Menu |
 

From: ghudson@mit.edu
Subject: git commit

Suggest unlocked iteration for mkey rollover

In database.rst when discussing the procedure for master key rollover,
suggest using unlocked iteration for large databases. Also make it
clear that unavailability due to locking during iteration is specific
to DB2.

https://github.com/krb5/krb5/commit/e71f4dcb5e4cc0e100caa75a8d2835dac2a6a32d
Author: Greg Hudson <ghudson@mit.edu>
Commit: e71f4dcb5e4cc0e100caa75a8d2835dac2a6a32d
Branch: master
doc/admin/database.rst | 10 +++++++---
1 files changed, 7 insertions(+), 3 deletions(-)
From: tlyu@mit.edu
Subject: git commit

Suggest unlocked iteration for mkey rollover

In database.rst when discussing the procedure for master key rollover,
suggest using unlocked iteration for large databases. Also make it
clear that unavailability due to locking during iteration is specific
to DB2.

(cherry picked from commit e71f4dcb5e4cc0e100caa75a8d2835dac2a6a32d)

https://github.com/krb5/krb5/commit/6ad31738bb440d068315ba00bd24b87a969d448f
Author: Greg Hudson <ghudson@mit.edu>
Committer: Tom Yu <tlyu@mit.edu>
Commit: 6ad31738bb440d068315ba00bd24b87a969d448f
Branch: krb5-1.15
doc/admin/database.rst | 10 +++++++---
1 files changed, 7 insertions(+), 3 deletions(-)