summaryrefslogtreecommitdiff
path: root/source4/cluster/ctdb/server
AgeCommit message (Collapse)AuthorFilesLines
2008-12-29s4:cluster: remove old/broken ctdb codeStefan Metzmacher15-7699/+0
We don't need a full copy of ctdb... If we want to readd cluster support, we should just use a ctdb client library. metze
2008-09-16Use single copy of tdb in both samba3 and samba4.Jelmer Vernooij10-10/+10
2008-06-14Use a custom init function for samba4 that sets a samba4Simo Sorce3-3/+3
specific debug function. By default do not debug, this is the most appropriate action for a library as we cannot assume what stderr is use for in the main app. The main app is responsible to set ev_debug_stderr if they so desire. (This used to be commit e566a2f308ac6fb4b526a744f7059b565670aea5)
2007-12-21r26101: remove some unused includesJelmer Vernooij7-7/+1
(This used to be commit bc615162fc515a8b8ae59af14cb1e80497e9afdd)
2007-10-10r23806: update Samba4 with the latest ctdb code.Andrew Tridgell15-0/+7705
This doesn't get the ctdb code fully working in Samba4, it just gets it building and not breaking non-clustered use of Samba. It will take a bit longer to update some of the calling ctdb_cluster.c code to make it work correctly in Samba4. Note also that Samba4 now only links to the client portion of ctdb. For the moment I am leaving the ctdbd as a separate daemon, which you install separately from http://ctdb.samba.org/. (This used to be commit b196077cbb55cbecad87065133c2d67198e31066)