Environment, for remote script

[David Bandel]

On 6/19/07, Dirk Moolman <DirkM at agilitytech.co.za> wrote:
> Sorry, my fault.   I thought it was not picking up the correct variable,
> but the person that set up the remote env file (setenv.sh), made a typo
> in one of his variables, and used a lower case letter in one of the
> PATHs, instead of uppercase.
>
> Interesting thing is, on the local server (the client), the path uses a
> lowercase letter in this case, and on the remote server the same path
> was set up using uppercase - took me a while to figure this out.
>
> This is what happens when you don't stick to naming conventions .....

These are bad habits from Windoze that doesn't differentiate between
upper and lower case for path names and doesn't use standard
conventions like white space as argument separators (only Bill Gates
knows what ridiculous convention he invented to parse a command line).

Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
            - Nemesis Air Racing Team motto