| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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)
|
| |
|
|
| |
(This used to be commit 6ac86f8be7d9a8c5ab396a93e6d1e6819e11f173)
|
| |
|
|
| |
(This used to be commit e53e79eebef3ece6978f0a2b4a1ee0a0814bb5d2)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
| |
(This used to be commit 40c0919aaa9c1b14bbaebb95ecce53eb0380fdbb)
|
| |
|
|
| |
(This used to be commit 84b468b2f8f2dffda89593f816e8bc6a8b6d42ac)
|
|
|
(This used to be commit 3633f862b966866819c9a0a6ad0238a858e15e62)
|
