6 Commits

Author	SHA1	Message	Date
Jelmer Vernooij	b6ffad3860	r14094: Use saner module directory names, fix loading of server service modules.	2007-10-10 13:56:49 -05:00
Jelmer Vernooij	bca0e8054f	r13655: Use new name of build header	2007-10-10 13:52:05 -05:00
Jelmer Vernooij	70e7449318	r12608: Remove some unused #include lines.	2007-10-10 13:49:03 -05:00
Jelmer Vernooij	c92ace494f	r12499: Move smb_build.h out of includes.h	2007-10-10 13:47:45 -05:00
Jelmer Vernooij	b6d2ad4ce0	r12494: Support loading modules from .so files for most subsystems. ... We now use a different system for initializing the modules for a subsystem. Most subsystems now have an init function that looks something like this: init_module_fn static_init[] = STATIC_AUTH_MODULES; init_module_fn *shared_init = load_samba_modules(NULL, "auth"); run_init_functions(static_init); run_init_functions(shared_init); talloc_free(shared_init); I hope to eliminate the other init functions later on (the init_programname_subsystems; defines).	2007-10-10 13:47:45 -05:00
Stefan Metzmacher	455b5536d4	r7643: This patch adds a new NTPTR subsystem: ... - this is an abstraction layer for print services, like out NTVFS subsystem for file services - all protocol specific details are still in rpc_server/spoolss/ - like the stupid in and out Buffer handling - checking of the r->in.server_name - ... - this subsystem can have multiple implementation selected by the "ntptr providor" global-section parameter - I currently added a "simple_ldb" backend, that stores Printers, Forms, Ports, Monitors, ... in the spoolss.db, and does no real printing this backend is basicly for testing, how the spoolss protocol works - the interface is just a prototype and will be changed a bit the next days or weeks, till the simple_ldb backend can handle all calls that are used by normal w2k3/xp clients - I'll also make the api async, as the ntvfs api this will make things like the RemoteFindFirstPrinterChangeNotifyEx(), that opens a connection back to the client, easier to implement, as we should not block the whole smbd for that - the idea is to later implement a "unix" backend that works like the current samba3 code - and maybe some embedded print server vendors can write there own backend that can directly talk to a printer without having cups or something like this - the default settings are (it currently makes no sense to change them :-): ntptr providor = simple_ldb spoolss database = $private_dir/spoolss.db metze	2007-10-10 13:18:16 -05:00