Just FYI:
On Win-XP, your product startup script nicely
finds drivers via the CLASSPATH environ variable.
But, on my Linux box (Debian, using BASH shell),
it does not.
I debugged the startup script and found my own workaround.
My solution is to add the option '--login' to the first line
of the script, so it now reads something like:
#! /bin/sh --login
(I believe there is a shorter-form option of just '-l'...
which is the letter 'el', but in many fonts, it can be
easily visually mistaken for a 'one'.)
This makes 'sh' run as a 'login' shell, and THEN it will
read the system's '/etc/profile' (where I have my CLASSPATH
defined).
I'm all set...happy with this workaround. You folks may
well come up with a better more precise fix for the general case.
Cheers and regards...
Dave
web-homepage: http://mysite.verizon.net/david.hubert.cook/homepage/home.htm
web-kayak-project:
http://mysite.verizon.net/david.hubert.cook/homebuilt-kayak/
web-GoogleMaps-project:
http://mysite.verizon.net/david.hubert.cook/google-maps/
|