diff options
| author | Ken Raeburn <raeburn@mit.edu> | 2008-06-23 20:09:53 +0000 |
|---|---|---|
| committer | Ken Raeburn <raeburn@mit.edu> | 2008-06-23 20:09:53 +0000 |
| commit | b08d1214e7e277e2fa8020b77aa62dc5244ca124 (patch) | |
| tree | dcc550aef0b053655bf01fc9e69af551740d8c69 | |
| parent | 417c99ad944f0cff2bbb527e7d79b010ebc41343 (diff) | |
| download | krb5-b08d1214e7e277e2fa8020b77aa62dc5244ca124.zip krb5-b08d1214e7e277e2fa8020b77aa62dc5244ca124.tar.gz krb5-b08d1214e7e277e2fa8020b77aa62dc5244ca124.tar.bz2 | |
more notes, on thread safety and logging
git-svn-id: svn://anonsvn.mit.edu/krb5/branches/sun-iprop@20456 dc483132-0cff-0310-8789-dd5450dbe970
| -rw-r--r-- | doc/iprop-notes.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/iprop-notes.txt b/doc/iprop-notes.txt index 8d701f3..f1e7940 100644 --- a/doc/iprop-notes.txt +++ b/doc/iprop-notes.txt @@ -116,6 +116,17 @@ but if we break log-format compatibility with Sun at some point, use the chance to make the kdb_ent_header_t offsets be more strictly aligned in the file. (16 or 32 bytes?) +Not thread safe! The kdb5.c code will get a lock on the update log +file while making changes, but the lock is per-process. Currently +there are no processes I know of that use multiple threads and change +the database. (There's the Novell patch to make the KDC +multithreaded, but the kdc-kdb-update option doesn't currently +compile.) + +Logging in kpropd is poor to useless. If there are any problems, run +it in debug mode ("-d"). You'll still lose all output from the +invocation of kdb5_util dump and kprop run out of kadmind. + Before merge: * investigate locking * check service princ |