A response to another poster peaked my curiosity.
> Incidentally, there is no reason to make it a bash
> script rather than vanilla sh, and you can simplify the script by using
> exec:
I have been writing shell scripts for a bit over fourteen
years so I am not new to this, but I unfortunately get caught up in
solving the problem of the moment and therefore fail to learn as much
as could be learned.
Is it just more efficient in resources to use plain #! /bin/sh
rather than bash?
I usually always write my shell scripts with the Bourne shell
unless I discover that something doesn't work in sh but does work in
bash and then I use bash.
Some arithmetic functions seem to be easier to code in bash
but that might also be because I didn't know the magic syntax to make
them work in sh.
Martin McCormick WB5AGZ Stillwater, OK
OSU Information Technology Division Network Operations Group
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
