Hi, this sounds truly odd somehow. For a start, a process on Linux or Unix inherits all environment variables from its parent process. Afterwards some programs have their own means of chaning the inherited set
bash uses an assignment like X=1 csh uses setenv fvwm uses SetEnv Changing a variable in a parent process, can never influence variable in a child process *which is already running*. Consequenly your only options are a) indeed completely start FVWM anew or b) use the built in functionality SetEnv. A third possibility might be that the whole story above is irrelevant for your problem if you are referring to shells started from within FVWM and they, for whatever reason, do not read .cshrc as you may be thinking. Put an 'echo here is .cshrc' at the top of .cshrc and check under which circumstances it is indeed read. Cheers, Harald. Am 11.07.2007 19:59 schrieb [EMAIL PROTECTED]: > All: > > I'm using v2.5.21. > > I have environment variables being set from users' .cshrc files. FVWM > is therefore started with that specific environment. However, if an > environment variable changes, the user needs to logout and back in > again for FVWM to see that new value. > > Is there a way to have FVWM re-read that value without logging out and > back in again? I have tried a FVWM restart, but that doesn't pick it > up. > > Thanks for any help. > -- --------------+--------------------------------------------- Harald Kirsch | pifpafpuf bei gmx punkt de
