sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
Code
f63f9053ef
samba-mirror/ctdb/config/ctdb.init

165 lines
3.2 KiB
Plaintext
Raw Normal View History

Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
#!/bin/sh
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
# Start and stop CTDB (Clustered TDB daemon)
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
#
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
# chkconfig: - 90 01
From Abhijith Das <adas@redhat.com>: Fixup the initscript sdo it passes rpm-lint (This used to be ctdb commit f84d0a9a8c7e9589e8833f21e1f977a0adab356b)
2008-08-25 04:13:18 +04:00
#
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
# description: Starts and stops CTDB
# pidfile: /var/run/ctdb/ctdbd.pid
# config: /etc/sysconfig/ctdb
make the packaging much more portable - tested on SLES9 and RHEL4 (This used to be ctdb commit 9521e3eee42b11303a2d6e0f5c05d0c0de4292d8)
2007-06-01 17:25:33 +04:00
### BEGIN INIT INFO
From Abhijith Das <adas@redhat.com>: Fixup the initscript sdo it passes rpm-lint (This used to be ctdb commit f84d0a9a8c7e9589e8833f21e1f977a0adab356b)
2008-08-25 04:13:18 +04:00
# Provides: ctdb
Add missing $remote_fs LSB dependency (This used to be ctdb commit a0b965bb73777dde7a4abf80c5c4742581bce520)
2013-08-29 10:20:05 +04:00
# Required-Start: $local_fs $syslog $network $remote_fs
# Required-Stop: $local_fs $syslog $network $remote_fs
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
From Abhijith Das <adas@redhat.com>: Fixup the initscript sdo it passes rpm-lint (This used to be ctdb commit f84d0a9a8c7e9589e8833f21e1f977a0adab356b)
2008-08-25 04:13:18 +04:00
# Short-Description: start and stop ctdb service
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
# Description: Start and stop CTDB (Clustered TDB daemon)
make the packaging much more portable - tested on SLES9 and RHEL4 (This used to be ctdb commit 9521e3eee42b11303a2d6e0f5c05d0c0de4292d8)
2007-06-01 17:25:33 +04:00
### END INIT INFO
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
# Source function library.
if [ -f /etc/init.d/functions ] ; then
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
# Red Hat
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
. /etc/init.d/functions
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
elif [ -f /etc/rc.d/init.d/functions ] ; then
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
# Red Hat
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
. /etc/rc.d/init.d/functions
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
elif [ -f /etc/rc.status ] ; then
# SUSE
more portability tweaks in the init script (This used to be ctdb commit 83a1c79e95af93a9ccfe78556ac5692c0315a3e4)
2007-06-03 11:53:26 +04:00
. /etc/rc.status
rc_reset
LC_ALL=en_US.UTF-8
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
elif [ -f /lib/lsb/init-functions ] ; then
# Debian
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
. /lib/lsb/init-functions
fi
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
# Avoid using root's TMPDIR
unset TMPDIR
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
[ -n "$CTDB_BASE" ] || export CTDB_BASE="/etc/ctdb"
cope with non-standard install dirs in event scripts (This used to be ctdb commit 52fff5345873690a9cc86495f414343eaa3bd540)
2007-09-14 08:14:03 +04:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
. "${CTDB_BASE}/functions"
ctdb-scripts: Split CTDB configuration loading loadconfig() currently tries to load the CTDB configuration and also any system configuration relevant to the current (event) script. Instead add a new function load_system_config() to load the distribution-specific system configuration for a component. Call this directly in the rare scripts that need the system configuration. Also call load_system_config when loading the CTDB configuration to pull in anything from the CTDB system configuration. This is partly for backward compatibility but also to get options that can be used anywhere. loadconfig() no longer takes an argument. It simply loads the CTDB configuration. Drop support for falling back to /etc/ctdb/sysconfig/ctdb (or similar). Surely there's nobody who uses that! Also, drop the indirection where loadconfig() calls _loadconfig(). This was used years ago as a test hook and is no longer required. Inexplicably, this change introduces a new shellcheck test failure, so silence this. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-02-06 03:25:56 +03:00
load_system_config "network"
make the init scripts more portable about location of system config files (This used to be ctdb commit 65f3e2bc722e314b2c51c3bfdc544b408a8a64cf)
2007-06-03 16:07:07 +04:00
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
# check networking is up (for redhat)
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
if [ "$NETWORKING" = "no" ] ; then
exit 0
fi
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
ctdb-scripts: Split CTDB configuration loading loadconfig() currently tries to load the CTDB configuration and also any system configuration relevant to the current (event) script. Instead add a new function load_system_config() to load the distribution-specific system configuration for a component. Call this directly in the rare scripts that need the system configuration. Also call load_system_config when loading the CTDB configuration to pull in anything from the CTDB system configuration. This is partly for backward compatibility but also to get options that can be used anywhere. loadconfig() no longer takes an argument. It simply loads the CTDB configuration. Drop support for falling back to /etc/ctdb/sysconfig/ctdb (or similar). Surely there's nobody who uses that! Also, drop the indirection where loadconfig() calls _loadconfig(). This was used years ago as a test hook and is no longer required. Inexplicably, this change introduces a new shellcheck test failure, so silence this. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-02-06 03:25:56 +03:00
load_system_config "ctdb"
ctdb.init: use detect_init_style() in the init script and export CTDB_INIT_STYLE, so that event scripts as called by ctdbd can use it. Michael (This used to be ctdb commit 56a10594ea9e44e3f034ac11161fd06e5ae46544)
2009-01-16 15:28:19 +03:00
detect_init_style
export CTDB_INIT_STYLE
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
ctdbd="${CTDBD:-/usr/sbin/ctdbd}"
ctdbd_wrapper="${CTDBD_WRAPPER:-/usr/sbin/ctdbd_wrapper}"
ctdb-scripts: Drop CTDB_PIDFILE configuration option Use environment variables for test-only options. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:26:07 +03:00
pidfile="/var/run/ctdb/ctdbd.pid"
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
############################################################
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
start()
ctdbd: Remove command-line option --debug-hung-script Use an environment variable instead. This just means that the initscript exports CTDB_DEBUG_HUNG_SCRIPT and the code checks for the environment variable. The justification for this simplification is that more debug options will be arriving soon and we want to handle them consistently without needing to add a command-line option for each. So, the convention will be to use an environment variable for each debug option. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 0581f9a84e58764d194f4e04064c2c5b393c348b)
2013-02-05 08:49:52 +04:00
{
ctdb-scripts: Avoid shellcheck warning SC2039 (echo -n) SC2039: In POSIX sh, echo flags are not supported. echo -n is well supported but the changes are simple. Improve some logic, replace some instances with printf. Who knew printf was in POSIX? Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2016-07-06 23:41:27 +03:00
printf "Starting ctdbd service: "
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
case "$CTDB_INIT_STYLE" in
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
suse)
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
startproc \
ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:02:40 +03:00
"$ctdbd_wrapper" "start"
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
rc_status -v
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
;;
redhat)
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
daemon --pidfile "$pidfile" \
ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:02:40 +03:00
"$ctdbd_wrapper" "start"
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
RETVAL=$?
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
echo
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/ctdb || RETVAL=1
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
return $RETVAL
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
;;
Revert "try to restart statd everytime it fails, not just the first time" This reverts commit 4f7b39a4871af28df1c4545ec37db179fa47a7da. (This used to be ctdb commit db7b96304e4725f29b12398b7582e385daed63ed)
2009-09-15 13:33:35 +04:00
debian)
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
eval start-stop-daemon --start --quiet --background --exec \
ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:02:40 +03:00
"$ctdbd_wrapper" "start"
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
;;
esac
From Sumit Bose <sbose@redhat.com> Fixes for init script to meet guidelines (This used to be ctdb commit 9f484404030211df85a215fd2280568a2ec020fb)
2010-02-22 06:06:52 +03:00
}
When we run the init script to start the ctdb service Use tdbdump to verify that all persistent database files are good before we start the daemon. (This used to be ctdb commit 13d3eb9a8bc7fad14fcd3e7e023c1336657424d6)
2008-05-12 10:44:33 +04:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
stop()
{
ctdb-scripts: Avoid shellcheck warning SC2039 (echo -n) SC2039: In POSIX sh, echo flags are not supported. echo -n is well supported but the changes are simple. Improve some logic, replace some instances with printf. Who knew printf was in POSIX? Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2016-07-06 23:41:27 +03:00
printf "Shutting down ctdbd service: "
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
case "$CTDB_INIT_STYLE" in
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
suse)
ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:02:40 +03:00
"$ctdbd_wrapper" "stop"
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
rc_status -v
;;
redhat)
ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:02:40 +03:00
"$ctdbd_wrapper" "stop"
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
RETVAL=$?
ctdb-scripts: Avoid shellcheck warning SC2015 (A && B || C) SC2015: Note that A && B || C is not if-then-else. C may run when A is true. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2016-07-06 13:40:23 +03:00
# Common idiom in Red Hat init scripts - success() always
# succeeds so this does behave like if-then-else
# shellcheck disable=SC2015
initscript: when stopping on Red Hat use the success/failure functions. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit bf5402b41282da94fee1ab3e4546ec089ff12f37)
2009-10-16 09:35:56 +04:00
[ $RETVAL -eq 0 ] && success || failure
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
echo ""
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/ctdb
return $RETVAL
;;
debian)
ctdb-scripts: Drop PID file argument from wrapper Use the default compile-time PID file. Use a CTDB_PIDFILE environment variable when testing. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:02:40 +03:00
"$ctdbd_wrapper" "stop"
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
log_end_msg $?
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
;;
esac
}
make sure vars are set at startup before recovery (This used to be ctdb commit 2c789f19b069c975c133dd8488b566a6715a8e76)
2008-01-04 04:41:53 +03:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
restart()
{
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
stop
start
From Sumit Bose <sbose@redhat.com> Fixes for init script to meet guidelines (This used to be ctdb commit 9f484404030211df85a215fd2280568a2ec020fb)
2010-02-22 06:06:52 +03:00
}
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
check_status ()
{
ctdb-scripts: Drop init script PID directory backward compatibility This tries to be backward compatible with very old versions of CTDB, so don't bother. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:01:17 +03:00
case "$CTDB_INIT_STYLE" in
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
suse)
ctdb-scripts: Drop init script PID directory backward compatibility This tries to be backward compatible with very old versions of CTDB, so don't bother. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:01:17 +03:00
checkproc -p "$pidfile" "$ctdbd"
rc_status -v
;;
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
redhat)
ctdb-scripts: Drop init script PID directory backward compatibility This tries to be backward compatible with very old versions of CTDB, so don't bother. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:01:17 +03:00
status -p "$pidfile" -l "ctdb" "$ctdbd"
;;
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
debian)
ctdb-scripts: Drop init script PID directory backward compatibility This tries to be backward compatible with very old versions of CTDB, so don't bother. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
2018-03-05 13:01:17 +03:00
status_of_proc -p "$pidfile" "$ctdbd" "ctdb"
;;
esac
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
}
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
############################################################
Add a hoook to the ctdb initscript that we can call out to for applications that want to track and produce audit logs when someone runs "service ctdb <something>" S1033891 (This used to be ctdb commit 4f4fbd4080a3a7226d3b82637f803c4b71217d39)
2012-02-06 05:07:08 +04:00
Eventscript argument cleanups and introduction of ctdb_standard_event_handler. The functions file no longer causes a side-effect by doing a shift. It also doesn't set a convenience variable for $1. All eventscripts now explicitly use "$1" in their case statement, as does the initscript. The absence of a shift means that the takeip/releaseip events now explicitly reference $2-$4 rather than $1-$3. New function ctdb_standard_event_handler handles the status and setstatus events, and exits for either of those events. It is called via a default case in each eventscript, replacing an explicit status case where applicable. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit 3d55408cbbb3bb71670b80f3dad5639ea0be5b5b)
2009-12-01 09:43:47 +03:00
case "$1" in
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
start)
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
start
;;
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
stop)
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
stop
;;
From Sumit Bose <sbose@redhat.com> Fixes for init script to meet guidelines (This used to be ctdb commit 9f484404030211df85a215fd2280568a2ec020fb)
2010-02-22 06:06:52 +03:00
restart|reload|force-reload)
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
restart
;;
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
status)
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
check_status
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
;;
From Sumit Bose <sbose@redhat.com> Fixes for init script to meet guidelines (This used to be ctdb commit 9f484404030211df85a215fd2280568a2ec020fb)
2010-02-22 06:06:52 +03:00
condrestart|try-restart)
initscript: Use a PID file to implement the "status" option Using "ctdb ping" and "ctdb status" is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the "status" option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then "service ctdb status" will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> Reviewed-by: Michael Adam <obnox@samba.org> (This used to be ctdb commit 687e2eace4f48400cf5029914f62b6ddabb85378)
2013-04-15 09:18:12 +04:00
if check_status >/dev/null ; then
restart
fi
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
;;
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
cron)
add an easy way to setup ctdb to start/stop samba (This used to be ctdb commit b0d9f427d83aff5b9a5c54b7b7c9d45d418e2352)
2007-06-02 12:51:05 +04:00
# used from cron to auto-restart ctdb
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
check_status >/dev/null 2>&1 || restart
add an easy way to setup ctdb to start/stop samba (This used to be ctdb commit b0d9f427d83aff5b9a5c54b7b7c9d45d418e2352)
2007-06-02 12:51:05 +04:00
;;
Initscript cleanups. * Move building of CTDB_OPTIONS to new function build_ctdb_options() and have it use a helper function for readability. * New functions check_persistent_databases() and set_ctdb_variables(). * Remove valgrind-specific stop code, since the general pkill should kill ctdbd when running under valgrind. * Remove some bash-isms (e.g. >& /dev/null) since the script is /bin/sh. * Make indentation consistent. * Minor clean-ups. Signed-off-by: Martin Schwenke <martin@meltin.net> Conflicts: config/ctdb.init (This used to be ctdb commit bebb21f18e3026cb78a306104e92ee005d1077b2)
2009-07-07 07:45:19 +04:00
*)
initscript: Simpify initscript and control CTDB via new ctdbd_wrapper Currently the initscript is very complex. This makes it hard to read and hard to add support for new init systems, such as systemd. Create a wrapper called ctdbd_wrapper to be installed alongside ctdbd. This is called by the initscript to start and stop ctdbd. It does the ctdbd option construct and waits until ctdbd is properly initialised before it exits. Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit e3abc7eebab5cceddc4ce7817890dd5db9be3450)
2013-07-09 09:22:07 +04:00
echo "Usage: $0 {start|stop|restart|reload|force-reload|status|cron|condrestart|try-restart}"
Inital rpm build files (This used to be ctdb commit 8830592b9202d6edab16af5c717608096597c517)
2007-05-28 00:48:18 +04:00
exit 1
esac
Copy Permalink