summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| * server: we don't need to copy strings we pass as talloc_asprintf() argumentsStefan Metzmacher2010-01-201-4/+4
| | | | | | | | | | | | metze (This used to be ctdb commit 080ba5ac2195fb73ef6f18740abdde57a7b97151)
| * events: 10.interfaces allow multiple interfaces per public addressStefan Metzmacher2010-01-201-1/+1
| | | | | | | | | | | | metze (This used to be ctdb commit f9837f8b6f887d28f29aeb3eeffe8cfb423b40b4)
| * server: allow multiple interfaces comma separated in public_addressesStefan Metzmacher2010-01-203-17/+47
| | | | | | | | | | | | metze (This used to be ctdb commit 33a00ef7233051acdbc66410130ec5d876a8422f)
| * server: add a ctdb_vnn_iface_string() helper function to access vnn->ifaceStefan Metzmacher2010-01-201-15/+26
| | | | | | | | | | | | metze (This used to be ctdb commit 9e5532e215892b2e0aadd9b106a730727f92c62e)
| * server: add a ctdb_set_single_public_ip() helper functionStefan Metzmacher2010-01-203-13/+26
| | | | | | | | | | | | metze (This used to be ctdb commit 400b4806c4a9686a2ee6398b5d7c3e0ca0793fd1)
| * config: add 13.per_ip_routing event scriptStefan Metzmacher2010-01-204-0/+435
| | | | | | | | | | | | | | | | | | With this script it's possible to generate routing tables per public ip address. metze (This used to be ctdb commit ff5678fbec2daef461143acf00cef3f94d7655fc)
| * config: add some ipv4 helper shell functionsStefan Metzmacher2010-01-201-0/+64
| | | | | | | | | | | | | | | | | | Many thanks to Michael Adam <obnox@samba.org> for the basic work. metze (This used to be ctdb commit ff9c641763702ae99632bbf4d0825d578440c074)
| * config: add interface_modify.sh and call it under flock to make modification ↵Stefan Metzmacher2010-01-205-55/+106
| | | | | | | | | | | | | | | | | | | | | | on interfaces atomic When two releaseip events run in parallel it's possible that the 2nd script readds a secondary ip that was removed by the 1st script. metze (This used to be ctdb commit e02417b2a55c45ac2c125b1b3463c9c39e7bc07a)
| * events/10.interfaces: move some parts to helper functionsStefan Metzmacher2010-01-201-28/+59
| | | | | | | | | | | | metze (This used to be ctdb commit 24cd42769d8f32b90a8876a6a08a36ab23076cd1)
| * config/functions: add tickle_tcp_connections()Stefan Metzmacher2010-01-201-0/+30
| | | | | | | | | | | | metze (This used to be ctdb commit 2397f13d7b5ca3847ef148187c6b179d06f6a47a)
| * server: add "init" eventStefan Metzmacher2010-01-2012-10/+44
| | | | | | | | | | | | | | | | | | This is needed because the "startup" event runs after the initial recovery, but we need to do some actions before the initial recovery. metze (This used to be ctdb commit e953808449c102258abb6cba6f4abf486dda3b82)
| * server: setup fault handler to get the build-in backtrace supportStefan Metzmacher2010-01-201-0/+1
| | | | | | | | | | | | | | | | The panic action feature will be added later. metze (This used to be ctdb commit 37d11895e96ba8bc8c9ba159083970c45f76d9bb)
| * lib/util: add pre and post panic action hooksStefan Metzmacher2010-01-202-0/+13
| | | | | | | | | | | | metze (This used to be ctdb commit e366e77ba170d2c27110c56004ae1adf97abef9e)
| * lib/util: import fault/backtrace handling from samba.Stefan Metzmacher2010-01-2011-2/+1307
| | | | | | | | | | | | metze (This used to be ctdb commit 8171d66f0061fe23ed6dfef87ffe63bfc19596eb)
| * configure: don't overwrite AC_CHECK_FUNC_EXT and AC_CHECK_LIB_EXTStefan Metzmacher2010-01-201-8/+0
| | | | | | | | | | | | | | | | This has curently no affect on the generated configure and config.h.in files. metze (This used to be ctdb commit 9d39ada437b02d84b70a5fea78b61bbb32f16d81)
| * move DEBUG* macros to one placeStefan Metzmacher2010-01-203-4/+4
| | | | | | | | | | | | metze (This used to be ctdb commit 4b4dd5d7f81bf226e05c7f3d40087043da1517a2)
| * tools/ctdb: display INACTIVE status in "ctdb status" and "ctdb status -Y"Stefan Metzmacher2010-01-201-3/+5
| | | | | | | | | | | | metze (This used to be ctdb commit 18af37e99ef8ff5623161495be432abfe5e3407f)
| * server: add missing goto again after do_recovery()Stefan Metzmacher2010-01-201-0/+2
| | | | | | | | | | | | metze (This used to be ctdb commit 898894d3acbcc0add2ab0706a3172a446622f687)
| * lib/events: finish "Run only one event for each epoll_wait/select call"Stefan Metzmacher2010-01-203-33/+2
| | | | | | | | | | | | | | | | | | | | This finished commit a78b8ea7168e5fdb2d62379ad3112008b2748576. The logic was missing in events_standard (the one that's used by default). metze (This used to be ctdb commit 49f0488a5e60c74b6b8361dffcd09ebb2db740f0)
* | initscript: handle spaces in option values inserted into $CTDB_OPTIONS.Martin Schwenke2010-01-221-7/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This puts single quotes around everything and uses eval on the command-lines that actually start ctdbd. The eval causes the single quotes to be interpreted. The "redhat" init style no longer uses the Red Hat daemon function. It loses the quoting and re-splits on spaces. Instead we add an extra line that uses the success/failure functions to keep things pretty. Note that this means that we don't respect daemon's $DAEMON_COREFILE_LIMIT variable but we do our own core file handling with $CTDB_SUPPRESS_COREFILE anyway. daemon's core file handling was probably overriding what we were doing anyway, so this can be regarded as a bug fix. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 9a9b36149042d4d8f455959582ec5c882162266a)
* | onnode: update algorithm for finding nodes file.Martin Schwenke2010-01-211-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2 changes: * If a relative nodes file is specified via -f or $CTDB_NODES_FILE but this file does not exist then try looking for the file in /etc/ctdb (or $CTDB_BASE if set). * If a nodes file is specified via -f or $CTDB_NODES_FILE but this file does not exist (even when checked as per above) then do not fall back to /etc/ctdb/nodes ((or $CTDB_BASE if set). The old behaviour was surprising and hid errors. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 6b5a5bb62369284585057caf09f05d2d5e3b9927)
* | onnode - respect $CTDB_BASE rather than hard-coding /etc/ctdb.Martin Schwenke2010-01-211-3/+5
|/ | | | | | Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit a9aa2e06774e8cd59a86d3343d3da2a2769561b5)
* source the nfs sysconfig file from the 61.nfstickles scriptRonnie Sahlberg2010-01-201-0/+2
| | | | (This used to be ctdb commit 085d1bea78fabf754ef6dd6d323f74a1d361e45c)
* document the in-memory ringbuffer for logging and the commandsRonnie Sahlberg2010-01-156-402/+422
| | | | | | used to set it up and manage it. (This used to be ctdb commit 037e64e1900f09e699d5fce50df2850f26f47f91)
* Make the size of the in memory ringbuffer for keeping the recent log messagesRonnie Sahlberg2010-01-155-6/+32
| | | | | | | | configureable using --log-ringbuf-size=<num-entries>. Add an entry in the sysconfig file to set this persistently. (This used to be ctdb commit c79c2da69bc352f509e7fca4b9172a4b7f23c0f8)
* new version 1.0.113Ronnie Sahlberg2010-01-131-1/+3
| | | | (This used to be ctdb commit 4bcb07c412260147cd926452287885d05b2344c1)
* Merge commit 'metze/master-for-ronnie'Ronnie Sahlberg2010-01-131-43/+34
|\ | | | | | | (This used to be ctdb commit 4cc9c79bfced9efa0d3817021512c86ed2fa3516)
| * server: call event_add_fd at the end of ctdb_set_child_logging()Stefan Metzmacher2010-01-121-20/+28
| | | | | | | | | | | | metze (This used to be ctdb commit 608e0765130aa9bca0aa77db5a888c413867a3fd)
| * ctdb_logging: simplify ctdb_fork_with_logging a lot and reduce the syscall usageStefan Metzmacher2010-01-121-23/+6
| | | | | | | | | | | | metze (This used to be ctdb commit acb98c36a3d56fa6b34747015b913ada3eaa133f)
* | New version 1.0.112.Martin Schwenke2010-01-121-1/+4
| | | | | | | | | | | | Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 64ae8b0702cfdc44a778e0cc3705dd685f9f6ab0)
* | Revert "Use wbinfo --ping-dc isntead of wbingo -p sicne this is a more ↵Martin Schwenke2010-01-121-1/+1
| | | | | | | | | | | | | | | | | | | | reliable way to determine if winbindd is in a useful state." This reverts commit 7c95e56ba871a4e0cb893a5cb5d821e7ff6e6dd6. wbinfo --ping-dc is proving too unreliable. (This used to be ctdb commit b70021856e76df1ba407c83cfc19bf332fbfc869)
* | Revert "events/50.samba: only use wbinfo --ping-dc if available"Martin Schwenke2010-01-121-6/+1
| | | | | | | | | | | | | | | | This reverts commit 7b73834ba3ac197cc8a3020c111f9bb2c567e70b. wbinfo --ping-dc is proving too unreliable. (This used to be ctdb commit 178f429a7b6d1008d35e857b6ca1df6adb60d255)
* | Merge commit 'origin/master'Martin Schwenke2010-01-072-38/+73
|\| | | | | | | (This used to be ctdb commit bb9fc8b4388848863fa2b8735bd77eb07b7b5849)
| * New version 1.0.111Ronnie Sahlberg2009-12-181-1/+4
| | | | | | | | (This used to be ctdb commit 484ae893f2179bebd0e2a2efe5f9619a39e48227)
| * eventscript: fix bug when script is abortedRusty Russell2009-12-181-1/+8
| | | | | | | | | | | | | | | | | | | | Another corner case when we terminate running monitor scripts to run something else: logging can flush the output and we write to a NULL pointer. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit eb22c34bccc8a04fcf63efa2bc48d9788709382e)
| * eventscript: remove cb_status, fix uninitialized bug when monitoring abortedRusty Russell2009-12-181-36/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (Reapplied with merge after accidental revert) Previously we updated cb_status a each script finished. Since we're storing the status anyway, we can calculate it by iterating the scripts array itself, providing clear and uniform behavior on all code paths. In particular, this fixes a longstanding bug when we abort monitor scripts to run some other script: the cb_status was uninitialized. In this case, we need to hand *something* to the callback; 0 might make us go healthy when we shouldn't. So we use the last status (normally, this will be the just-saved current status). In addition, we make the case of failing the first fork for the script and failing other script forks the same: the error is returned via the callback and saved for viewing through 'ctdb scriptstatus'. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 2c84fe393ff2b961abf77d58a371c24db5ecb93b)
* | Merge commit 'origin/master'Martin Schwenke2009-12-1885-2108/+5266
|\| | | | | | | (This used to be ctdb commit 82e1c5231c389bea935328a08ecf9b0b3a3979ef)
| * Version 1.0.110Ronnie Sahlberg2009-12-181-1/+4
| | | | | | | | (This used to be ctdb commit 859e18db681dabe0990793d03f58e59a061aa8bb)
| * eventscript: fix cleanup path when setting up script listRusty Russell2009-12-181-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | We shouldn't set ctdb->current_monitor until we set destructor: that's what cleans it up. Also, free state->scripts on no-scripts exit path: it's not a child of state because we need it in the destructor. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 843a2ed5ef85f628788b0caf7417c6b61b5c6d3f)
| * server: add set_close_on_exec() on more fdsStefan Metzmacher2009-12-171-0/+3
| | | | | | | | | | | | metze (This used to be ctdb commit 7101ae80bf4e530f48e31e4c58707aa45a9fd3d5)
| * server: fix fd leaks in the new logging codeStefan Metzmacher2009-12-171-2/+5
| | | | | | | | | | | | metze (This used to be ctdb commit 140070dd81b39545fe2d56f70e9b9c96bfdae07f)
| * version 1.0.109Ronnie Sahlberg2009-12-172-55/+43
| | | | | | | | (This used to be ctdb commit 99894a70fe2ebfe43daae7e88ff0fc9cab33e0fb)
| * eventscript: remove cb_status, fix uninitialized bug when monitoring abortedRusty Russell2009-12-171-29/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we updated cb_status a each script finished. Since we're storing the status anyway, we can calculate it by iterating the scripts array itself, providing clear and uniform behavior on all code paths. In particular, this fixes a longstanding bug when we abort monitor scripts to run some other script: the cb_status was uninitialized. In this case, we need to hand *something* to the callback; 0 might make us go healthy when we shouldn't. So we use the last status (normally, this will be the just-saved current status). In addition, we make the case of failing the first fork for the script and failing other script forks the same: the error is returned via the callback and saved for viewing through 'ctdb scriptstatus'. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 5d50f0e16948d18009f6623f132113f7273efc7f)
| * fix a conflict in the merge from rustyRonnie Sahlberg2009-12-1711-66/+60
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge commit 'rusty/ctdb-no-setsched' Conflicts: server/ctdb_vacuum.c (This used to be ctdb commit b4365045797f520a7914afdb69ebd1a8dacfa0d9)
| | * ctdb: use mlockall, cautiouslyRusty Russell2009-12-165-1/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We don't want ctdb stalling due to paging; this can be far worse than scheduling delays. But if we simply do mlockall(MCL_FUTURE), it increases the risk that mmap (ie. tdb open) or malloc will fail, causing us to abort. This patch is a compromise: we mlock all current pages (including 10k of future stack for expansion) and then relock when a client asks us to open a TDB. We warn, but don't exit, if it fails. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 82f778e85440bc713d3f87c08ddc955d3cfce926)
| | * Remove RT priority, use niceness.Rusty Russell2009-12-165-56/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1) It's buggy. Code needs to be carefully written (ie. no busy loops) to handle running with it, and we fork and run scripts.[1] 2) It makes debugging harder. If ctdbd loops (as has happened recently) it can be extremely hard to get in and see what's happening. We've already seen the valgrind hacks. 3) We have seen recent scheduler problems. Perhaps they are unrelated, but removing this very unusual setup is unlikely to hurt. 4) It doesn't make anything faster. Under all but the most perverse of circumstances, 99% of the cpu gives the same performance as 100%, and we will always preempt normal processes anyway. [1] I made this worse in 0fafdcb8d353 "eventscript: fork() a child for each script" by removing the switch_from_server_to_client() which restored it, but even that was only for monitor scripts. Others were run with RT priority. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 482c302d46e2162d0cf552f8456bc49573ae729d)
| | * Add --valgringing flag instead of --nosetschedRusty Russell2009-12-168-10/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The do_setsched was being tested for whether to mmap tdbs: let's make it explicit. We can also happily move the kill-child eventscript hack under this flag. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (This used to be ctdb commit 2ee86cc1f311d7b7504c7b14d142b9c4f6f4b469)
| * | fix conflict in merge from metzeRonnie Sahlberg2009-12-1674-1967/+4813
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge commit 'metze/master-tdb-check' Conflicts: server/ctdb_vacuum.c (This used to be ctdb commit 82421f20dcad4b0e25f109583879a26c0ee9c465)
| | * | doc: regenerate manpagesStefan Metzmacher2009-12-164-287/+536
| | | | | | | | | | | | | | | | | | | | | | | | metze (This used to be ctdb commit e3825407a509110c786d618efcdfa56ba93380a5)
| | * | doc: fix docbook warnings for ctdb.1 and onnode.1 manpagesStefan Metzmacher2009-12-162-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | metze (This used to be ctdb commit 0d1300aa2325c94d8fb1c3cf8d454e5eee43dde9)
generated by cgit (git 2.34.1) at 2025-10-02 21:20:11 +0000