<br>Maybe <br><br>#!/usr/bin/env bash <br><br>instead of<br><br>#!/bin/bash<br><br>will solve the uncertainities of localization<br><br><br><div><span class="gmail_quote">2007/2/21, Glynn Clements <<a href="mailto:glynn@gclements.plus.com">
glynn@gclements.plus.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Hamish wrote:<br><br>> 2) keep #!/bin/sh, but add this within the script:
<br>><br>> if [ -z "$BASH" ] ; then<br>> echo "$0: This script requires Bash." 1>&2<br>> exit 1<br>> fi<br><br>Or:<br> if [ -z "$BASH" ] ; then<br> exec bash "$0" "$@"
<br> echo "$0: This script requires Bash." 1>&2<br> exit 1<br> fi<br><br>AFAICT, that should work so long as bash is called "bash" (and not<br>e.g. "bash2" or "
bash-3.1.17") and is somewhere in the path.<br><br>--<br>Glynn Clements <<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>><br><br>_______________________________________________<br>grass-dev mailing list
<br><a href="mailto:grass-dev@grass.itc.it">grass-dev@grass.itc.it</a><br><a href="http://grass.itc.it/mailman/listinfo/grass-dev">http://grass.itc.it/mailman/listinfo/grass-dev</a><br></blockquote></div><br>