Shell startup files aren't loaded in VNC session
A coworker is using VNC to do remote work on one of our Linux servers and
it seems that no terminal session started in VNC loads his startup files.
He's using tcsh (I know, I know) and has startup configs in ~/.setenv.
It appears that any terminal he starts is starting exactly at the point
(path, environment, etc) where he executed the vncserver command to start
the server. Modulo LD_LIBRARY_PATH being unset, presumably since vncserver
does setuid/setgid. Has anyone seen this? It's possible to work around it
but is very annoying.
His work flow is
Login to the RHEL server and run vncserver once.
In subsequent sessions:
Connect to VNC server
Start terminal, IDE, emacs, etc.
All applications seem to not see any environment file changes made since
vncserver was executed.
No comments:
Post a Comment