1833554 Members
3317 Online
110061 Solutions
New Discussion

env problem

 
Bruno Cunha
Frequent Advisor

env problem

Hello, after running /usr/dt/bin/dtsearchpath my env reads now new variables like XMICONBMSEARCHPATH and XMICONSEARCHPATH, this variables cause problems in java applications, my question is, how can I remove this variables from my env, I tried unset and works, but when I log or open a new windows and do a env the variables are still there, I assume that I have to edit some file, witch one ?

Thanks
Do it today, don't leave for tomorrow
6 REPLIES 6
CHRIS_ANORUO
Honored Contributor

Re: env problem

Go to /etc and edit the PATH file
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
Bruno Cunha
Frequent Advisor

Re: env problem

This env variables aren't in /etc/PATH
Do it today, don't leave for tomorrow
Bill McNAMARA_1
Honored Contributor

Re: env problem

You probably have a script from some prog exporting your PATH and including these to it.
find . * | xargs grep XMIWHATEVER
to find the script reexporting it.
Then analyse and edit the script.

You may want to limit the find to etc or the suspect file location

Later,
Bill
It works for me (tm)
Marcel Boon
Trusted Contributor

Re: env problem

Hi,

Maybe you can find it here.
/etc/dt/config/Xsession.d/

Marcel

ps. look at "man dtsearchpath"
See the man pages
Shannon Petry
Honored Contributor

Re: env problem

There is a pretty easy fix, depending on the users shell.
If it's c-shell, add this to the $HOME/.cshrc
if ( $?prompt ) then
unsetenv $VARS_TO_UNDEF
endif

This will unset variable's in an interactive shell. I would not flat out disable them, because many of the CDE applications rely on these variables.

I'd have to backtrack a bit for other shells, because a few years back, I went to an exclusive c-shell for user logins.

Regards,
Shannon
Microsoft. When do you want a virus today?
Bruno Cunha
Frequent Advisor

Re: env problem

Hello, I was unable (until now) to find the file that set this variables, but with the unset $VAR_NAME that Shannon write I was able to put that in the script that calls the java application and now it's working fine.

Thank you all
Do it today, don't leave for tomorrow