Age | Commit message (Collapse) | Author | Files | Lines |
|
was the initial cause of the connections database becoming corrupt.
Note that this bug only happens when doing deletions within a
traversal, which is why it has only showed up now
- added delete within traversal testing to tdbtorture
- added a lot more logging to tdb
(This used to be commit 6e1277df9d964c615a3ad876d3b89ff8132081c1)
|
|
can't be merged don't fail the operation, instead just add
it to the free list anyway
added logging to tdb
(This used to be commit dda086fdf92fded016afc785f7965a375faae5aa)
|
|
(This used to be commit 110ec9923bd2ad729d63f129514f3f1de76de9c1)
|
|
(This used to be commit d64456b5889f0ee3a8c2108c13789540bfc3d90c)
|
|
(This used to be commit 2d3e2f8877fb8eb21b4ccf4d7a56f1c625c71780)
|
|
- added TDB_CLEAR_IF_FIRST flag to clear the database if this is the
first attached process. Useful for non-persistent databases like our
locking area (this will also make upgrades to new database layouts easier)
- use lock_path() in a couple of places
- leave connections database open while smbd running
- cleaned up some tdb code a little, using macros for constants
(This used to be commit 00e9da3ca577527db392aced62f02c69cfee8f4f)
|
|
(This used to be commit 3b3fdd8661cc10057823be4c594e40ca615ca704)
|