Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
<node>.<pid>.<fd> to be unique in a prefork process environment.
Andrew Bartlett and David Disseldorp
(This used to be commit 931994a7f185bbc98924823e9e8cef1011dd0957)
|
|
(This used to be commit c863f4ebde8efa1a695b4469142d6719e30bc419)
|
|
(This used to be commit 7352206f4450fdf881b95bda064cedd9d2477e4c)
|
|
(This used to be commit 3809113d86dbd35b906356a05bb481a1e2bfe4b7)
|
|
(This used to be commit 1cb849dfba21b9b5d00b20ba8201f0e142bfeb07)
|
|
(This used to be commit 56dfcb4f2f8e74c9d8b2fe3a0df043781188a555)
|
|
(This used to be commit fd697d77c9fe67a00939a1f04b35c451316fff58)
|
|
(This used to be commit 37425495f392a2d0122a93aa2c42758eab7dab5a)
|
|
number in more places.
(This used to be commit df9cebcb97e20564359097148665bd519f31bc6f)
|
|
(This used to be commit abe8349f9b4387961ff3665d8c589d61cd2edf31)
|
|
(This used to be commit 08bb1ef643ab906f1645cf6f32763dc73b1884e4)
|
|
- disable the brlock ctdb backend for now
(This used to be commit b04bcf46e135af597b89994148a28275d29cdba6)
|
|
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)
|
|
There are still a few tidyups of old FSF addresses to come (in both s3
and s4). More commits soon.
(This used to be commit fcf38a38ac691abd0fa51b89dc951a08e89fdafa)
|
|
(This used to be commit 3633f862b966866819c9a0a6ad0238a858e15e62)
|
|
(This used to be commit d825f4e6cc96a365061805352a2df3818df2364e)
|
|
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 e2fe45cf4073b68e2a1c6577928d0765e26f3267)
|
|
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)
|
|
should now work on a real cluster, and not just a localhost simulator
(This used to be commit f05072ad74fb08fd906bc500c5e89930bcc3387f)
|
|
handling messages to remote nodes. Implemented dummy functions in the
'local' cluster backend for the messaging hooks, and modified the
messaging layer to check if the destination is remote and redirect
messages via the cluster layer
(This used to be commit 4474552e8fb73efebef32ad8480d7fe9a1e379ef)
|
|
standalone and built-in ctdb
(This used to be commit 3e5f29bddfd83914eeec706367b2b1bd30aba31e)
|
|
environment for subsystems that have not yet been converted to use
ctdb to get a shared temporary tdb
(This used to be commit 0ed91384497aed6817b2220c31344bfcd45fd033)
|
|
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)
|
|
(This used to be commit ba3ce8abe3457a1245fd4746af780c6055d39425)
|
|
it will be interesting to see how the build farm handles this
(This used to be commit 53be449630bd67d649a9e70cc7e25a9799c0616b)
|