r3586: Fix some of the issues with the module init functions.

Both subsystems and modules can now have init functions, which can be
specified in .mk files (INIT_FUNCTION = ...)

The build system will define :
 - SUBSYSTEM_init_static_modules that calls the init functions of all statically compiled modules. Failing to load will generate an error which is not fatal
 - BINARY_init_subsystems that calls the init functions (if defined) for the subsystems the binary depends on

This removes the hack with the "static bool Initialised = " and the
"lazy_init" functions
(This used to be commit 7a8244761bfdfdfb48f8264d76951ebdfbf7bd8a)

1 files changed, 4 insertions, 5 deletions

diff --git a/source4/smbd/process_model.c b/source4/smbd/process_model.c
index 3493425774..69e321e0c2 100644
--- a/source4/smbd/process_model.c
+++ b/source4/smbd/process_model.c
@@ -118,18 +118,17 @@ const struct process_model_critical_sizes *process_model_version(void)
 /*
   initialise the PROCESS_MODEL subsystem
 */
-BOOL process_model_init(void)
+NTSTATUS process_model_init(void)
 {
 	NTSTATUS status;
 
 	status = register_subsystem("process_model", register_process_model); 
 	if (!NT_STATUS_IS_OK(status)) {
-		return False;
+		return status;
 	}
 
-	/* FIXME: Perhaps panic if a basic process model, such as simple, fails to initialise? */
-	static_init_process_model;
+	process_model_init_static_modules;
 
 	DEBUG(3,("PROCESS subsystem version %d initialised\n", PROCESS_MODEL_VERSION));
-	return True;
+	return NT_STATUS_OK; 
 }