sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-10 01:18:15 +03:00
Code
ad8eb45fe2
samba-mirror/ctdb/config
History
Martin Schwenke ad8eb45fe2 initscript: Check that rc.ctdb is executable before running it 
Signed-off-by: Martin Schwenke <martin@meltin.net>

(This used to be ctdb commit 59a47c0674bacfebc17a1b44f0244727bf2fa7a4)
2012-10-18 20:05:43 +11:00
..
events.d Revert "Eventscripts - add facility to 10.interface to delete unmanaged IPs" 2012-10-18 20:05:42 +11:00
ctdb-crash-cleanup.sh Fix ctdb-crash-cleanup sysconfig handling 2011-12-06 11:55:46 +11:00
ctdb.init initscript: Check that rc.ctdb is executable before running it 2012-10-18 20:05:43 +11:00
ctdb.sysconfig Debug: When scripts hang, we may need to collect additional data in order to debug why the script hung. 2012-05-17 10:29:03 +10:00
debug-hung-script.sh Debug: When scripts hang, we may need to collect additional data in order to debug why the script hung. 2012-05-17 10:29:03 +10:00
functions config/functions: fix a comment 2012-10-17 21:56:58 +02: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: Fix a bug in the calculations of $STATE 2012-07-26 21:24:15 +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.