X-Git-Url: https://git.madduck.net/code/molly-guard.git/blobdiff_plain/ecdbd1cb447dca36108ca5fe0c4c6d366a09ae70..799bd85d7475f6c888b90d9cad0b7e3eed8d1164:/shutdown?ds=inline

diff --git a/shutdown b/shutdown
index c68b572..387aacb 100755
--- a/shutdown
+++ b/shutdown
@@ -47,6 +47,18 @@ usage()
 	   terminal, and the actual command to execute is does not involve
            --help or is \`shutdown -c'.
 
+	  $ME will always interpose the prompt if the environment variable
+          ALWAYS_MOLLY is set to '1'.  This variable may be set in the file
+	  /etc/default/${ME} .
+
+        - Print out a warning message with information about this host
+	  before the action takes place.  You can use:
+		/etc/molly-guard.<Action>.message
+	  To print out a message specific to the command you're trying to
+	  use.  Or:
+		/etc/molly-guard.message
+	  For a general warning message.
+
 	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
@@ -95,7 +107,7 @@ case "$CMD $ARGS" in
     ;;
 esac
 
-run-parts --exit-on-error $CHECK_ARGS /usr/share/molly-guard/checks.d
+run-parts --exit-on-error --arg $CMD $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