IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The IRIX make does not like lines with only whitespace. With LIBNETAPI_LIBS
evaluating to nothing this happens there.
(This used to be commit 225fbe743c)
library on top of the Samba 3 RPC library:
* dcerpc_pipe_connect
* dcerpc_ndr_request_recv
* dcerpc_ndr_request_send
These are the main functions used by the generated client calls in Samba
4.
(This used to be commit 3501778242)
The dispatcher takes a config source argument in the form
of "backend:path" where backend can (currently) be one of
"txt" (aka "file") or "reg" (aka "registry").
When the path is omitted, it is up to the backend to provide
a default path.
When there is no separator ":" and the string is not a recognized
backend, then file backend is assumed and the string is passed
in as the path argument.
Michael
(This used to be commit cc613a60eb)
This backend can be used untill ctdb knows about real
transactions.
It stores a master tdb in a shared location and a readonly copy
on the local harddisk. Reads are always on the local tdb
and writes always on both. Change notify messages are send
to all message context, which ask for them. With the notifies
it's possible to just update the changed records, instead of
copying all records (which is the fallback).
You need to configure:
dbwrap:use_tdb2=yes
dbwrap_tdb2:master directory=/some/shared/path
dbwrap_tdb2:local directory=/var/lib/samba
metze
(This used to be commit aa6230de0d)
The interface is like that of net rpc registry.
Access is direct local access to the registry tdb through reg_api.
Michael
(This used to be commit 3250068eb9)
This is a simple implementation of text backend for libsmbconf.
It is read only. It uses the parser from params.c. It loads the
given config file and holds the parsed lists of strings in memory.
Config is only re-read if the time stamp of the config file has changed.
Brilliant performance on large files is not to be expected since the
string lists are not hashed. This might be added in the future.
Michael
(This used to be commit 4ea5084385)
Stick to hand-written headers (that are there anyways).
Add some missing prototypes to util_tdb.h and dbwrap.h.
I did not bother to add a header for each single dbwrap backend
open function but put the prototypes for the open functions into
the central dbwrap.h.
Michael
(This used to be commit edf4dbed27)
Remaining problem is that not all *.syms linker scripts are generated
so the LD command needs to look in a single place. Out of tree
builds now work but report write access to the source tree in order
to create the $(srcdir)/expotrs/libtdb.sysms file.
(This used to be commit 6e9287c5c3)
IMO there is no need to imitate a custom registry backend.
Only default regdb hooks are used here, so a plain initialization
of regdb should suffice.
This way, only reg_api is used in libgpo, and no registry
backend code is visible.
Michael
(This used to be commit 10ae8accb4)
The libnet_conf code to access the registry based configuration has
become more of a library used in several places in samba (e.g. loadparm)
than an abstraction of "net conf". So I move it to a location lib/smbconf/.
In the same breath, the api is fixed (not generated by make proto anymore).
Michael
(This used to be commit 5315ef41f4)
This reverts commit 3a0f781352.
This needs more thought.
Setting RPATH like this does not work on all supported
platforms (Linux, Solaris and AIX seem to work, HP-UX,
Tru64 and MacOS don't, MacOS doesn't even seem to have
an rpath at all prior to 10.4).
What is more, rpath also has some bad effects (when
updating libraries, e.g.), so it should not be set
unconditionally.
I will come up with a confiugure mechanism to control this.
For now, just use the LDFLAGS environment variable if
you want to use an rpath.
Sorry for any inconveniences.
Michael
(This used to be commit 6850dc242b)
- James suggested using gcc's "deprecated" attribute to mark the context
structure fields to generate warnings. This creates a scenario with the
best of all worlds. I'm able to move to an organization that more easily
allows future enhancements, while avoiding any mandatory changes by
applications. Thanks, James!
- Updated WHATSNEW.txt so that it accurately reflects the current state of
affairs.
Derrell
(This used to be commit a67f96fbe9)
The libsmbclient interface has suffered from difficulty of improvement and
feature enrichment without causing ABI breakage. Although there were a number
of issues, the primary ones were:
(a) the user of the library would manually manipulate the context structure
members, meaning that nothing in the context structure could change other
than adding stuff at the end;
(b) there were three methods of setting options: setting bits in a flags field
within the context structure, setting explicit options variables within an
options structure in the context structure, and by calling the
smbc_option_set() function;
(c) the authentication callback did not traditionally provide enough
information to the callee which required adding an option for a callback
with a different signature, and now there are requests for even more
information at the callback, requiring yet a third signature and option to
set it (if we implement that feature).
This commit provides a reorganization of the code which fixes (a) and (b).
The context structure is now entirely opaque, and there are setter and getter
functions for manipulating it. This makes maintaining ABI consistency much,
much easier.
Additionally, the options setting/getting has been unified into a single
mechanism using smbc_option_set() and smbc_option_get().
Yet to be completed is a refactoring of the authentication callback (c).
The test programs in examples/libsmbclient have been modified (if necessary;
some applications require no changes at all) for the new API and a few have
been minimally tested.
Derrell
(This used to be commit d4b4bae8de)
This reverts commit 9b47a73290.
libnet_join.idl should not be processed along with the other idl files
since it should not produce server and client code, just the header.
Michael
(This used to be commit 2967b29f23)
This is used for two purposes:
First, I'm using it to test the async I/O code. In the forked process it is
pretty easy to delay a reply for a random amount of time. See the
BUILD_FARM_HACKS snippet.
Second, there are systems around that claim to have Posix AIO but which is
broken. This might be some help for those systems.
Also add tests how to pass file descriptors
(This used to be commit b0e52cecf2)
Jerry, I checked this very carefully that nothing got lost. The only thing I need to
re-add still is the normalized DN handling for account precreation in "net ads join".
Guenther
(This used to be commit a5c6347644)
This replaces the original hand-written tdb code, now that the
linking dependencies have been significantly reduced.
Michael
(This used to be commit d08a3a1957)
This removes the internals of reg_api from srv_winreg_nt.c entirely,
only reg_api is used there, now. This enlarges the dependencies of
reg_api somewhat now since it adds regfio. But this can be separated
out later. The current goal is to achieve a complete use of reg_api.
Michael
(This used to be commit 2222acbac9)
This adds a general mechanism to create version-scripts for
linking shared libraries from one or several header files,
similar to mkproto.sh/awk.
Michael
(This used to be commit 65817703c4)
This should work with m4_include(lib/tdb/libtdb.m4) like already
done with talloc, but currently this does not work (yet) - tdb
code has to be merged from s4 before that.
Michael
(This used to be commit e92fdf6b20)
smbd doesn't need $(WBCOMMON_OBJ) anymore,
it works with any libwbclient.so now
and may talk to an older winbindd.
metze
(This used to be commit e3435930a3)
And only link in wb_common.o directly into binaries
which really need it.
Note: It's important that $(WBCOMMON_OBJ) comes before
@LIBWBCLIENT_STATIC@ overwise we may try to
link in wb_common.o twice.
metze
(This used to be commit 135d9dd6d8)
This also establishes a general configure mechanism to control static vs
dynamic linking of internal subsystems built as libraries:
This first simple approach is as follows.
* It applies only to "subsystems" that we build as libraries and for
that linking samba against the libraries (as opposed to linking in
the plain object files) has been configured in Makefile.in.
* If we do build the shared library, then we link dynamically by default.
* We only link statically if we don't build shared or if the library
appears in the new --with-static-libs configure option
(comma-separated list).
Example (currently only one):
--with-static-libs=talloc makes use of libtalloc.a instead
of linking the dynamic variant with -ltalloc.
A possilble way to setup linking against libraries in Makefile.in is this:
For a subsystem, "mylib" say, we build bin/libmylib.a and bin/libmylib.so.
The subsystem usually has a MYLIB_OBJ definition in Makefile.in. Define
LIBMYLIB_STATIC=bin/libmylib.a and and LIBMYLIB_LIBS=-lmylib in configure.in
as controlled by presence of "mylib" in the list given to --with-static-libs
and change uses of $(MYLIB_OBJ) to @LIBMYLIB_STATIC@ in Makefile.in and
add @LIBMYLIB_LIBS@ to the link targets as needed.
In the example of talloc, which is needed everywhere, I have simply
added @LIBTALLOC_LIBS@ to the definition of "LIBS" in Makefile.in.
For other subsystems, one will have to be more careful.
Michael
(This used to be commit 71b990d9d6)
Logging of the ldap libraries appears with a [LDAP] prefix
inside the samba logs. This is controlled by two new parameters:
* "ldap debug level" sets the debug level of the ldap libraries.
It is the bit-field as understood by the openldap server.
* "ldap debug threshold" is the samba debug level at which ldap
logging appears inside the samba logs.
This probably needs some configure tests since it makes
use of the LBER_OPT_LOG_PRINT_FN option to redirect the
debug output of the ldap libraries.
Michael
(This used to be commit 15c25990bd)
This actually is a counterpart to reg_init_full, in that is does
open and initialize the registry too, but only registeres the backends
necessary to access the SMBCONF key.
Michael
(This used to be commit 01bda3ab35)
reg_openpath should be used instead of this function (along with the
reg_api interface). Last callers of this function are in services_db.c
Michael
(This used to be commit 0005b88d74)
This is an effect of the removal of the dynamic registry overlay.
This is the beginning of a restructuring of registry linkage in Makefile.in.
Michael
(This used to be commit 7453e78a8e)
Make sure to only respond to the exact current version key since subkeys
are registered by other backends (printing and - soon - perflib).
Michael
(This used to be commit 2c650bf63c)
Store streams in posix xattrs. A kludge, as xattrs are limited in many ways,
but it might be a help for some situations.
(This used to be commit 83a805220e)
This is an option for file systems that do not implement xattrs: in
lockdir/eas.tdb an array of xatts per inode is stored.
It can not solve the problem that xattrs might reappear if a posix-level
process deletes a file and happens to re-create it under the same name. On file
systems with birthtime we might have a chance to detect this, but not with
standard posix. A future version might put relief on file systems that do have
xattrs but where these are severely limited in size/speed/whatever: We can put
a simple marker as a native xattr, but the xattrs proper are stored in the tdb.
Volker
(This used to be commit 2036b4c5ad)
This patch adds the configure option --enable-libwbclient-shared that defaults
to yes. If you set --enable-developer=yes, then you can say
--enable-libwbclient-shared=no to avoid problems you might have with the wrong
shared libaries.
Jerry, is this acceptable to you? If yes, please push.
Thanks!
Volker
(This used to be commit 7a88cd61e0)
Also, don't auto-generate prototypes of the (two) exported functions
but make a start in having handwritten prototypes in dedicated header
files (not in includes.h ... :-)
Michael
(This used to be commit 395f29d8b7)
