Adding the variable to environments without determining that is the environment the code is running in is rather bad form.
You'd do better to write a separate script to print out the running environment and evaluate if it sees it. That actually tells you something about your environment and doesn't pollute a namespace without cause. On Tue, Jul 28, 2015 at 8:14 PM, Ken Stephens <[email protected]> wrote: > Rich Shepard wrote: > > On Tue, 28 Jul 2015, Rich Shepard wrote: > > > >> Don't recall. Worth a second try. > > Made certain the variable was exported with the version quoted and > not > > quoted and still no joy. > > > > Thanks, Wes, > > > > Rich > Rich, > > When I expect a variable to be in the environment and it isn't, I > usually find that the application has shelled out of my environment and > into anothers. This happens when I use root to install an application, > which is usually required. Have your tried to add the variable into the > root's environment? > > Ken > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
