]>
git.madduck.net Git - code/molly-guard.git/blobdiff - shutdown
madduck's git repository
Every one of the projects in this repository is available at the canonical
URL git://git.madduck.net/madduck/pub/<projectpath> — see
each project's metadata for the exact URL.
All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@ git. madduck. net .
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
SSH access, as well as push access can be individually
arranged .
If you use my repositories frequently, consider adding the following
snippet to ~/.gitconfig and using the third clone URL listed for each
project:
[url "git://git.madduck.net/madduck/"]
insteadOf = madduck:
EXEC="/sbin/$CMD"
case "$CMD" in
EXEC="/sbin/$CMD"
case "$CMD" in
+ halt|reboot|shutdown|poweroff )
if [ ! -f $EXEC ]; then
echo "E: $ME: not a regular file: $EXEC" >&2
exit 4
if [ ! -f $EXEC ]; then
echo "E: $ME: not a regular file: $EXEC" >&2
exit 4
- case "$ARGS" in
- (*--molly-guard-do-nothing*)
- ARGS0="${ARGS%%--molly-guard-do-nothing*}"
- ARGS1="${ARGS##*--molly-guard-do-nothing}"
- echo "$ME: would run: $EXEC $ARGS0 $ARGS1"
- exit 0;;
- *) exec $EXEC "$ARGS";;
- esac
-}
+ cat <<-_eousage
+ Usage: $ME [options]
+ (shielding $EXEC)
-# require $SSH_CONNECTION to be set, indicates an SSH session
-[ -n "${SSH_CONNECTION:-}" ] || do_real_cmd
-# require an interactive terminal connected to stdin
-test -t 0 || do_real_cmd
-# pass through help commands
-case "$CMD $ARGS" in
- (shutdown\ *-c*) do_real_cmd;;
- (*-h*) do_real_cmd;;
- *) :;;
-esac
+ Instead of invoking $EXEC directly, $ME will run a number of checks
+ to guard against accidental shutdowns/reboots.
+ Some of the checks available are:
+ - Prompt the user for the machine's if the current shell is a child
+ of an SSH connection (or --pretend-ssh) has been given on the
+ command line, if the shell is connected to an interactive
+ terminal, and the actual command to execute is does not involve
+ --help or is \`shutdown -c'.
-sigh()
-{
- echo "Good thing I asked; I won't $CMD $HOSTNAME ..."
- exit 2
+ Only if the user satisfies all the checks will $ME take action.
+ Specifying --molly-guard-do-nothing as argument to the command will
+ make $ME echo the command it would execute rather than actually executing
+ it.
+
+ The actual command's help output follows:
+
+ _eousage
-trap 'echo;sigh' 1 2 3 9 10 12 15
+ARGS=
+DO_NOTHING=0
+CHECK_ARGS=
+for arg in "$@"; do
+ case "$arg" in
+ (*-molly-guard-do-nothing) DO_NOTHING=1;;
+ (*-help)
+ usage 2>&1
+ eval $EXEC --help 2>&1
+ exit 0
+ ;;
+ (*-pretend-ssh) CHECK_ARGS="${CHECK_ARGS:+$CHECK_ARGS }--arg --pretend-ssh";;
+ *) ARGS="${ARGS:+$ARGS }$arg";;
+ esac
+done
+
+do_real_cmd()
+{
+ if [ $DO_NOTHING -eq 1 ]; then
+ echo "$ME: would run: $EXEC $ARGS"
+ exit 0
+ else
+ eval exec $EXEC "$ARGS"
+ fi
+}
-echo "$ME: SSH session detected!"
-echo -n "Please type in hostname of the machine to $CMD: "
-read HOSTNAME_USER || :
+if [ $DO_NOTHING -eq 1 ]; then
+ echo "I: demo mode; $ME will not do anything due to --molly-guard-do-nothing. "
+fi
-[ "$HOSTNAME_USER" = "$HOSTNAME" ] || sigh
+# pass through certain commands
+case "$CMD $ARGS" in
+ (*shutdown\ *-c*)
+ echo "I: executing $CMD $ARGS regardless of check results."
+ do_real_cmd
+ ;;
+esac
+run-parts --exit-on-error $CHECK_ARGS /usr/share/molly-guard/checks.d
+# run-parts won't return to us if there are failures, but I'm paranoid.
+if [ $? == 0 ]; then
+ do_real_cmd
+ exit
+fi