summaryrefslogtreecommitdiff
path: root/source4/cluster/ctdb/common
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r21256: - msg_type is not needed in the cluster messaging APIAndrew Tridgell2-1/+10
- merge ctdb_get_num_nodes() from bzr tree (This used to be commit 3df7527aedeba7ce2f4a6ca2d3b7167f58c6b68a)
2007-10-10r21232: added a raw ctdb messaging api - allowing ctdb applications to takeAndrew Tridgell3-13/+109
advantage of the ctdb messaging layer for their own data (This used to be commit b288ba05e5dc2aa5c8cd26eaee1c41b12e4996da)
2007-10-10r21172: fixed a commentAndrew Tridgell1-1/+2
(This used to be commit 2d6e082e813e18dcd43bc8d9a8f445f77e0a8452)
2007-10-10r21045: every call in brlock_ctdb ended up neededing a 32 bit status code, soAndrew Tridgell1-11/+20
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)
2007-10-10r21044: - merge struct ctdb_call API changes from bzr treeAndrew Tridgell1-76/+60
- convert brlock code to new API (This used to be commit cf317480cb715dbaab87c06f824a1db14b09b298)
2007-10-10r20991: use relative includes for ctdb headers. This works with bothAndrew Tridgell4-5/+4
standalone and built-in ctdb (This used to be commit 3e5f29bddfd83914eeec706367b2b1bd30aba31e)
2007-10-10r20945: fixed the bug causing locktest to fail with the ctdb backend after aAndrew Tridgell3-27/+8
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)
2007-10-10r20944: if a call has been destroyed before a reply comes in then discard theAndrew Tridgell1-0/+4
reply (This used to be commit 05d19af38c1e75ba65ed2755c6087df1f937ee2a)
2007-10-10r20943: use offsetof() instead of sizeof() - 1 for the packet lengthAndrew Tridgell1-14/+18
calculations. It will be interesting to see how portable this is. The advantage over the sizeof() method is that it avoids padding problems after the data[1] array. That was causing us to get valgrind errors. (This used to be commit fd8e46043903d3650f8f33dcab165800f6869b1d)
2007-10-10r20918: a bit more debugging, and remove the hackish /dev/null writes I usedAndrew Tridgell2-44/+12
to track down some uninitialised memory (sometimes valgrind gets the offset wrong, writing to /dev/null 1 byte at a time avoids this) (This used to be commit 4bf741b567417231c29606904aea2af0a91c941c)
2007-10-10r20901: - not all compiler like uint8_t data[0] elements!Stefan Metzmacher1-8/+8
- 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)
2007-10-10r20900: fix compiler warningsStefan Metzmacher1-0/+3
metze (This used to be commit cb59eae91966e3e493c3c992d2b96965d17dac17)
2007-10-10r20896: make the maximum lacount configurable in smb.confAndrew Tridgell2-1/+9
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)
2007-10-10r20889: import ctdb cluster backend from bzrAndrew Tridgell4-0/+1182
it will be interesting to see how the build farm handles this (This used to be commit 53be449630bd67d649a9e70cc7e25a9799c0616b)