4 Commits

Author	SHA1	Message	Date
Andrew Tridgell	5e54558c6d	r23784: use the GPLv3 boilerplate as recommended by the FSF and the license text ... (This used to be commit b0132e94fc)	2007-10-10 12:28:22 -05:00
Jeremy Allison	d824b98f80	r23779: Change from v2 or later to v3 or later. ... Jeremy. (This used to be commit 407e6e695b)	2007-10-10 12:28:20 -05:00
Jeremy Allison	72099d8f66	r23512: Fix conflict in #define for SECDESC_PREFIX. Ensure all ... reg #defines use "REG_" prefix. Michael - please check gcc warnings on compiles. Jeremy. (This used to be commit 7885b68bb5)	2007-10-10 12:23:23 -05:00
Michael Adam	aa4110e6f2	r23509: This activates the global options from the registry in loadparm. ... The global options are stored as values in the subkey "global" of the SMBCONF registry key. The activation is accomplished in smb.conf though a new special semantic of the "include" parameter: "include = registry" triggers the processing of the registry global options exactly at the position of the include statement. Options read from the registry take the same precedence as parameters loaded from a file via include. Need to reload the registry globals is detected by watching the tdb sequence number. Registry shares are automatically activated when the registry globals are processed. So a "registry only" configuration can be realized by an smb.conf that looks as follows: ================================ [global] include = registry ================================ The global options and registry shares can be conveniently edited with the "net conf" utility. Caveat: A possible pitfall consists in using "include = registry" together with the "lock directory" directive in the registry. This problem will be addressed in the next time. Note on the code: Processing of the registry options is accomplished by a function process_registry_globals() in loadparm.c The current version is only an interim solution: It is handcoded instead of using the infrastructure of reg_api.c. The reason for this is that using reg_api still has too large linker dependencies, bloating virtually all targets by PASSDB_OBJ, SMBLDAP_OBJ, GROUPDB_OBJ and LDB stuff. A version of process_registry_globals that uses reg_api is included but commented out. The goal is to eventually refactor and restructure the registry code so that one can use the reg_api to access only the registry tdb and not link all the dynamic backends with all their linking implications. (This used to be commit 24b0cbcb37)	2007-10-10 12:23:23 -05:00