Age | Commit message (Collapse) | Author | Files | Lines |
|
(This used to be commit 9f233c14540cd4b2d5f4c7fe01e2d89cb220abc8)
|
|
include fragments in the Samba 3 or 4 makefile.
(This used to be commit 6d54e9104de577ab727ee99a76e690a2fae71636)
|
|
(This used to be commit e779cf4724610b5d737102d1f55d1367744b188a)
|
|
(This used to be commit a5db115dc6827896c66fe08554b3fe7185eea52f)
|
|
Not sure if we can produce one from the other, so I manually made
them equal for now.
Michael
(This used to be commit 1c14c457bea75fb3055712547cca501e8ef3fc20)
|
|
(This used to be commit 9f402c607f44663cab91cc7d2139f62b84c99cc0)
|
|
(This used to be commit 5cc7a638e93e5f3540755b441a99d4fd3c9c7134)
|
|
(This used to be commit 6deca23b6c66616fbf5ba004e9b778aa68790df6)
|
|
A talloc pool is a chunk of memory that can be used as a context for further
talloc calls. Allocations with the pool as the parent just chew from that
memory by incrementing a pointer. If the talloc pool is full, then we fall back
to the normal system-level malloc(3) to get memory.
The use case for talloc pools is the transient memory that is used for handling
a single SMB request. Incrementing a pointer will be way faster than any malloc
implementation.
There is a downside of this: If you use talloc_steal() to move something out of
the pool, the whole pool memory is kept around until the last object inside the
pool is freed. So if you talloc_free() the pool, it might happen that the
memory is freed later. So don't hang anything off a talloc pool that should
live long.
Volker
(This used to be commit 60ef9a84f0bd18d48e453c08aa420d17275e0881)
|
|
Michael
(This used to be commit 2a2c28584cdb65fcea8563eb3bf21fea497fdff3)
|
|
Michael
(This used to be commit a0caedb94f6f7c62ae706e35a4c0b2876f74978d)
|
|
(This used to be commit 0c829e6ee6f43299cc5889c2af3d0402256da0d0)
|
|
mkconfig.mk file.
(This used to be commit 4cc93a98f984d322e41f403169cfa4945b469935)
|
|
Michael
(This used to be commit 3b9b396292077b2d3ff1fb1712462b767cc2bf81)
|
|
This code is no longer used, and equivalent code already exists in Python
(scripting/python/samba/samba3.py)
(This used to be commit c16212e8bf5343496ea4b3afc30a8b4d3a0afe2d)
|
|
(This used to be commit 5f33545c78e13871d622c0a5a0ded789bf624869)
|
|
(This used to be commit e4d7cd8ba77aa05c11dad457c3f2c2c6252c5966)
|
|
(This used to be commit 501259ff31641bf52e337b597881d1fedc6b2a63)
|
|
(This used to be commit dad809030478a85ac13a73bce9c07314792f01c2)
|
|
(This used to be commit 1868a42108012183aa78fe5d4f524d45f4505a3e)
|
|
(This used to be commit 9705263a6c58d4ade556d17db2009dbb85291b22)
|
|
(This used to be commit fd9cc4eb5afae8b255e753d480190b490cd3f7ab)
|
|
(This used to be commit b3e60a388d338ef90540007239e88563cb9ba27a)
|
|
We don't get this far in the test at the moment however.
Andrew Bartlett
(This used to be commit c3098d5c52505e143a6ce498273a5ce6a66220b0)
|
|
(This used to be commit df4efb902ec5053ae9d7c6e4fd1e21255ca66914)
|
|
structure. The BASE-TORTURE test found this problem - caused because
the messaging path was not unique.
If we didn't use a macro for cluster_id_equal(), we could make it
opaque, and avoid this...
Andrew Bartlett
(This used to be commit c3387545c57d2dd4922b4f3806b4552cee8035a3)
|
|
<node>.<pid>.<fd> to be unique in a prefork process environment.
Andrew Bartlett and David Disseldorp
(This used to be commit 931994a7f185bbc98924823e9e8cef1011dd0957)
|
|
DEBUG(), DEBUGADD() and friends can now use debug_ctx() in the
formatting expressions again,
e.g.
DEBUG(5,("Guid failed to match: %s\n", GUID_string(debug_ctx(), r->guid)));
Sadly it's done with macros (again) but when we need to save the 8 or 16
bytes of object code per DEBUG() expression we can do it the Samba 3 way
with added thread-safety for Samba 4. That could save up to 200K,
allowing 12 bytes for each occurrance of DEBUG...
Signed-off-by: Amin Azez <azez@ufomechanic.net>
(This used to be commit 9781967542b00c279563d435aec72dac1e8c7e9a)
|
|
(This used to be commit eb3af24926977208a8099c848a510704d2ae3524)
|
|
(This used to be commit 9f6ea4692ca79c607538871c597698b98abf13d0)
|
|
and default to using system smb.conf.
(This used to be commit b3afde0f00ab5093b577b139a062c233d4db2524)
|
|
(This used to be commit 91d7ba5202e6c375456a42c2c6861f63c7fcfc20)
|
|
(This used to be commit 676fd18fa2914b7b5530014a944a11ea1d6f631d)
|
|
(This used to be commit 5c64d4adaf50215ec2645f76e6c0335572147614)
|
|
(This used to be commit c8947fda23eb874a7694bdee1b4de605744c2769)
|
|
(This used to be commit 2fc26c09026a0f2f74e5c7c86002e662b559d265)
|
|
(This used to be commit da0952bdd6196b23200063cadd866b1d5551a65c)
|
|
(This used to be commit 9a5cc88b090125b45e61da1ea1c9ac52f5ff6ab2)
|
|
metze
(cherry picked from commit 2f460915111066d79f5dc9b4ae4d003918d06852)
(This used to be commit d2ac8be28d3aff59eddbdc6189a255a34c10d502)
|
|
easier and should also make it easier
to migrate to a new build system.
(This used to be commit 77b400764e3dadfa05407343af649ad9298cc085)
|
|
(This used to be commit 583ea85ae04c0bc2e70ab2e595e05f76f65c3be1)
|
|
(This used to be commit 7077df3e2e3f171532f6a5ac87d45201736c9c11)
|
|
(This used to be commit c54c087a19e36e0522eb4546c9425ae446f0628b)
|
|
(This used to be commit 98ebdbe52fd615ea62a3caa17acfe8bb31b8f85d)
|
|
first place.
(This used to be commit 434e4857cec17d6d9e8983e151c170eed59fc6d1)
|
|
starting with "New Key #1" and iterating up to "New Key #99" before giving up.
ldb_open_key() calls reg_path_to_ldb() to build the appropriate dn from the key
name. reg_path_to_ldb() was not catching the error returned by
ldb_dn_add_base_fmt() due to the unescaped '#' character, causing the returned
dn to be that of the parent key, not the potential new key. Additionally,
Windows expects a return value of WERR_BADFILE when a key does not exist, but
WERR_NOT_FOUND was being returned instead. Correcting the building of the dn
and the providing the expected return value allows new key creation to succeed.
When attempting to delete a key, Windows passes the complete path to the key,
not just the name of the child key to be deleted. Using reg_path_to_ldb() to
build the correct dn allows key deletion to succeed.
(This used to be commit d57792d67b865ef43e7f21640b158862627f4b45)
|
|
Rather than map the error returned by the registry to the correct error,
return the correct error in the first place.
Also deal with the fact that the right error code is now returned in a
couple of places.
(This used to be commit 1e31fcb8a097810a97e2d4bb1f243f1b34cc2415)
|
|
The '#' character was causing problems, as it was not being escaped for the dn,
but the failure returned by ldb_dn_add_child_fmt() was not being caught. This
was causing the new value to be added on the parent key, not the current key.
When attempting to delete the new value (now on the parent key) the same
escaping error was returned by ldb_dn_add_child_fmt(), causing the delete to
delete the key and not the value.
When attempting to rename a value, Windows first tries to ensure the new name
does not already exist. When a value does not exist, Windows expects a return
value of WERR_BADFILE, but WERR_NOT_FOUND was being returned instead.
Providing the WERR_BADFILE that Windows expects allows values to be renamed.
(This used to be commit 94fb39cfd967455ce5a554720c1c7e6183f91056)
|
|
There were a few cases left that attempted to detect errors from ldb_*()
function calls using "(ret < 0)". As all LDB_* error codes are greater than
zero, there was no chance any errors would be detected. Changed all such tests
to use "(ret != LDB_SUCCESS)".
(This used to be commit 0ed6f1b1628da5b922f02a5f9a6c60071b6277f2)
|
|
values better.
(This used to be commit c8b22ef30c7fc0ccc15e9fc9a38fdc639fc4b976)
|