1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-24 21:34:56 +03:00
samba-mirror/ctdb/config
Ronnie Sahlberg 02ebd35398 Merge remote branch 'martins/eventscripts'
(This used to be ctdb commit bb008c01989ebb173a3f095ebd2f90ab54f9da91)
2011-08-17 14:10:04 +10:00
..
events.d Merge remote branch 'martins/eventscripts' 2011-08-17 14:10:04 +10:00
ctdb-crash-cleanup.sh In the example script to remove all ip addresses after a ctdb crash, 2010-04-23 09:08:26 +10:00
ctdb.init When starting and stopping ctdb through the init-script, make sure we first clear all public ips bvefore we start the daemon, in case they are still hanging around since a previous kill -9 and also make sure we drop them after we have stopped the deamon when shutting down 2011-08-11 11:48:04 +10:00
ctdb.sysconfig Add documentation for the new filesystem use monitoring 2011-08-11 10:07:50 +10:00
functions Eventscripts - new default TCP port checker using "ctdb checktcpport" 2011-08-17 14:02:45 +10:00
gdb_backtrace lib/util: import fault/backtrace handling from samba. 2010-01-20 09:44:36 +01:00
interface_modify.sh Scripts: remove absolute paths from interface_modify.sh. 2011-08-08 15:50:10 +10:00
notify.sh server: add "setup" event 2010-02-23 10:38:49 +01:00
README Scripts: add note about not using absolute command paths to README. 2011-08-09 16:36:37 +10:00
statd-callout Eventscripts: remove unnecessary absolute paths from external commands. 2011-08-03 17:19:15 +10:00

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.

  interface_modify.sh

    Script to support add/remove IPs and other funky stuff.  Not sure
    why this is separate... but it certainly allows easy wrapping by
    flock.

  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.