mirror of
https://github.com/samba-team/samba.git
synced 2025-03-03 12:58:35 +03:00
dac075129b
When thousands of connections are being killed the logs are flooded with information about connections that should be killed. When some connections are not killed then the number not killed is printed. This is the wrong way around! When debugging "fail-back" problems, it is important to know details of connections that were *not* killed. It is almost never important to know the full list of all connections that were *supposed* to be killed. Instead, print a summary showing how many connections of the total were killed. If any were not killed then print a list of remaining connections. Update unit tests: infrastructure for fake TCP connections, existing, test cases, add new test cases. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
This directory contains run-time support scripts for CTDB.
Selected highlights:
ctdb.init
An initscript for starting ctdbd at boot time.
events.d/
Eventscripts. See events.d/README for more details.
functions
Support functions, sourced by eventscripts and other scripts.
statd-callout
rpc.statd high-availability callout to support lock migration on
failover.
Notes:
* All of these scripts are written in POSIX Bourne shell. Please
avoid bash-isms, including the use of "local" variables (which are
not available in POSIX shell).
* Do not use absolute paths for commands. Unit tests attempt to
replace many commands with stubs and can not do this if commands are
specified with absolute paths. The functions file controls $PATH so
absolute paths should not be required.