NEVERMIND, THIS DOESN'T WORK!

Some of the functions I wrote up in my StackScripts were so cool, I wanted to use them *after* the machine was installed. However, on a StackScript where there are <ssinclude> tags, it choked up bash.

So, we include the <ssinclude> tag in a quote that escapes the <> chars, then wrap the whole thing in a case statement that detects whether the script is being run from an interactive shell, or from a non-interactive one (first boot as a StackScript invokation):

case "$-" in
        *i*)
                PATH=$(cd ${0%/*} && pwd -P)
                source "${PATH}/bash_lib_rh.sh"
                source "${PATH}/drupal_lib_rh.sh"
        ;;
        *)
                source '<ssinclude StackScriptID="154">'
                source '<ssinclude StackScriptID="162">'
        ;;
esac

The only thing you have to do after using this code is to make sure you export your UDF variables before you run anything.[/code][/b]

You can use the tty command in a script to test if it's being run in an interactive shell. Just do tty > /dev/null and check the exit status:

Or use the "-t" test

if [ -t 0 ]
then
  echo STDIN is connected to a terminal
else
  echo No terminal
fi

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)