openafs/src/libafsauthent
Russ Allbery 3a34d8cb4f autoconf-likes-relative-paths-20060802
When using the install-sh that ships with the source tree, Autoconf
substitutes in a relative path just to be annoying.  Define the INSTALL
variables in each individual Makefile so that they find the proper file.
Remove the definitions from Makefile.config so that no one will
accidentally get the wrong ones.
2006-08-03 03:37:12 +00:00
..
.cvsignore add-cvsignores-to-project-20010910 2001-09-10 21:14:01 +00:00
afsauthent.def ubik-call-sucks-20060704 2006-07-04 22:22:35 +00:00
afsauthent.exp Initial IBM OpenAFS 1.0 tree 2000-11-04 02:13:13 +00:00
afsauthent.rc windows-file-versioning-20030619 2003-06-19 20:00:31 +00:00
Makefile.in autoconf-likes-relative-paths-20060802 2006-08-03 03:37:12 +00:00
mapfile libafsauthent-mapfile-update-20040823 2004-08-23 17:15:36 +00:00
NTMakefile windows-64-bit-type-safety-20051105 2005-11-06 09:29:36 +00:00
README Standardize License information 2000-11-04 10:01:08 +00:00

Copyright 2000, International Business Machines Corporation and others.
All Rights Reserved.

This software has been released under the terms of the IBM Public
License.  For details, see the LICENSE file in the top-level source
directory or online at http://www.openafs.org/dl/license10.html

This library is to be used by multithreaded programs that need to access
the kauth and auth library interfaces.  The primary method used to obtain
thread safety in these libraries is to lock/unlock a recursive global
mutex at the entry point of every public function in the library.

However, not all public functions are made thread safe since not all 
functions are needed by the NT admin work.  In particular, there are
many public functions that make up decendants of the functions
we wish to use that weren't modified, since these functions will be 
protected by the locking at a higher level function.

To prevent people from using non-thread safe functions, platform 
specific methods are used to limit the functions exported by the 
library (using def files under NT and mapfiles under Solaris).  For 
most non-exported functions, it should be trivial to make the 
transformation to thread safe by simply locking/ unlocking the 
global mutex at the beginning/end of the function.