| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
(This used to be commit 1ce32673d960c8b05b6c1b1b99e1976a402417ae)
|
|
(This used to be commit 1aa4628f16b4c2ba4c8253fdd9c109b3ea874c5a)
|
|
- use ctdb_attach() instead of ctdb_db_handle()
- make ctdb_attach() return an existing db handle if it exists
(This used to be commit be85c48f8d4a22fd4ed922be6f7f1979f349d291)
|
|
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)
|
|
This better fits the way Samba4 does message dispatch
(This used to be commit 2c12f8e72fb999f4f66700291dd4d7f6f73a8eae)
|
|
(This used to be commit 807b959082d3b9a929c9f6597714e636638a940e)
|
|
(This used to be commit d7f122df1dba30e46e84e294cccecb2e4ef82072)
|
|
(This used to be commit a57af1ff8234ab590ebf28b3316953bec880005c)
|
|
added opendb ctdb backend from ronnie
(This used to be commit b0da25cb79f860bfa14ba7a8419c7996d936292b)
|
|
existing ctdb_call() mechanism isn't sufficient. The main problem is
that the operations on the record need to be done with a lock held
while a local posix file operation is happening. We can't use a
ctdb_call callback function to do the actual file opens, renames,
unlinks etc as the callback would run on the wrong node.
So this commit adds the prototypes for two new ctdb API functions
which will make a opendb backend easier. Volker will probably
recognise these functions as they are basically the same as what he
did in his earlier Samba clustering code :-)
(This used to be commit d9a997fd390e4162c015435d1c703fb3a4978f2f)
|
|
ctdb backend to use the updated multi-database API
(This used to be commit 44dcac9e4d81bfc078512248967b6240db9d1bd8)
|
|
- merge ctdb_get_num_nodes() from bzr tree
(This used to be commit 3df7527aedeba7ce2f4a6ca2d3b7167f58c6b68a)
|
|
advantage of the ctdb messaging layer for their own data
(This used to be commit b288ba05e5dc2aa5c8cd26eaee1c41b12e4996da)
|
|
rather than allocating a reply_data field each time, I have changed
the ctdb_call API to include a status code. That greatly simplifies
use of the API.
(This used to be commit 70c3acaf8876fa5712e2135df234fe3bc1e32e77)
|
|
- convert brlock code to new API
(This used to be commit cf317480cb715dbaab87c06f824a1db14b09b298)
|
|
couple of hundred opertations. Also removed a lot of the debug code I
was using to track this down.
(This used to be commit 7622e7b4b2694ec14062d0f6de035b946106a6aa)
|
|
- this fix looks really ugly but I don't know a better solution...
if we would use uint8_t *data; then we would send the pointer value
also in the network packet and we would need to initialize
s->data = ((void *)(&s->data) + 1;
to make the memcpy statements work as they're currently,
so we use uint8_t data[1] in the struct definition ...
tridge: please review careful!
hopefully fix the build on solaris and HPUX
metze
(This used to be commit 015097677c8a65e9f5a4367f4f89193a4b2de76b)
|
|
metze
(This used to be commit cb59eae91966e3e493c3c992d2b96965d17dac17)
|
|
at the moment the brlock_ctdb backend will sometimes fail after
dmaster migrations. So to pass tests this needs to be set high. Thats
a priority to fix.
(This used to be commit 45f5c272f366f6a793941d97c9522c5b2b0cb639)
|
|
it will be interesting to see how the build farm handles this
(This used to be commit 53be449630bd67d649a9e70cc7e25a9799c0616b)
|
