sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
Code
642848b916
samba-mirror/ctdb/config
History
Martin Schwenke 642848b916 eventscripts: Remove unused function ctdb_check_counter_equal() 
Signed-off-by: Martin Schwenke <martin@meltin.net>

(This used to be ctdb commit fd536a26b310b5bf9628da62cca0b425f4a54030)
2013-05-06 15:45:10 +10:00
..
events.d ctdbd: Remove the "stopped" event 2013-05-06 13:38:21 +10:00
ctdb-crash-cleanup.sh scripts: Ensure even external scripts get tagged in logs as "ctdbd" 2013-04-22 13:58:36 +10:00
ctdb.init initscript: Look for tdbtool/tdbdump using which, not in fixed locations 2013-05-06 15:40:30 +10:00
ctdb.sudoers statd-callout: Make sure statd callout script always runs as root 2013-04-08 11:14:28 +10:00
ctdb.sysconfig doc: allows to -> allows one to 2013-01-22 18:03:35 +11:00
debug-hung-script.sh scripts: debug-hung-script.sh doesn't need functions/loadconfig 2013-01-08 15:18:47 +11:00
functions eventscripts: Remove unused function ctdb_check_counter_equal() 2013-05-06 15:45:10 +10:00
gcore_trace.sh common: Debug ctdb_addr_to_str() using new function ctdb_external_trace() 2012-10-18 20:05:42 +11:00
gdb_backtrace lib/util: import fault/backtrace handling from samba. 2010-01-20 09:44:36 +01:00
notify.sh server: add "setup" event 2010-02-23 10:38:49 +01:00
README Eventscript support - Remove unused interface_modify.sh 2012-03-22 15:30:27 +11:00
statd-callout statd-callout: Make sure statd callout script always runs as root 2013-04-08 11:14:28 +10:00

README 

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.