1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-25 23:21:54 +03:00
samba-mirror/ctdb/config
Martin Schwenke 171bef3d68 Eventscripts - new function ctdb_set_current_debuglevel()
This function ensures that CTDB_CURRENT_DEBUGLEVEL is set.  It works
like this:

1. If it is already set then do nothing, since it might have been set
   some other way.

   The recommended "other way" would be to add a file in rc.local.d/.

2. If it is not set then set it by sourcing
   /var/ctdb/eventscript_debuglevel.

3. If this file does not exist then create it using output from "ctdb
   getdebug".

If the optional 1st argument is set to "create" then don't source an
existing file but create a new one instead - this is useful for
creating the file just once in each event run in, say, 00.ctdb.

If there's a problem getting the debug level from ctdb then it is
silently set to 0 - no use spamming logs if our debug code is
broken...

Signed-off-by: Martin Schwenke <martin@meltin.net>

(This used to be ctdb commit 93910921c8a25f2b029733cd938069ff7c7bdab7)
2011-08-17 09:00:46 +10:00
..
events.d Eventscripts - ensure the statd update-trigger file always exists. 2011-08-16 13:28:40 +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 function ctdb_set_current_debuglevel() 2011-08-17 09:00:46 +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.