Here is the thing. All workstations in the network have the /etc/profile modified and set up to call a profile script in the network that sets up variables that we need here. Here $LD_LIBRARY_PATH and other variables get set, fixed, or modified to support our development process. The weird thing is that while in a TTY the $LD_LIBRARY_PATH is fine and retains its value. But if I log in to the gui (KDE, GNOME) then the $LD_LIBRARY_PATH is blank. I have greped the entire disk I can't find where is the $LD_LIBRARY_PATH is being overwritten, if that is what is happening.
Does anyone knows what's going on here?
Jean
Hi Jean,
If you login via GUI, it doesn't read/load you /etc/profile so user doesn't inherit the variable set on that, I forget where to specifically put it but it's set on Xxxxstartup something, also try to set it on bashrc as it's being read even on GUI login.
Hth,
/joseph
On 7/6/07, Jean Figarella jfigarella@vecna.com wrote:
Here is the thing. All workstations in the network have the /etc/profile modified and set up to call a profile script in the network that sets up variables that we need here. Here $LD_LIBRARY_PATH and other variables get set, fixed, or modified to support our development process. The weird thing is that while in a TTY the $LD_LIBRARY_PATH is fine and retains its value. But if I log in to the gui (KDE, GNOME) then the $LD_LIBRARY_PATH is blank. I have greped the entire disk I can't find where is the $LD_LIBRARY_PATH is being overwritten, if that is what is happening.
Does anyone knows what's going on here?
Jean _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Jul 05, 2007 at 06:42:54PM -0400, Jean Figarella alleged:
Here is the thing. All workstations in the network have the /etc/profile modified and set up to call a profile script in the network that sets up variables that we need here. Here $LD_LIBRARY_PATH and other variables get set, fixed, or modified to support our development process. The weird thing is that while in a TTY the $LD_LIBRARY_PATH is fine and retains its value. But if I log in to the gui (KDE, GNOME) then the $LD_LIBRARY_PATH is blank. I have greped the entire disk I can't find where is the $LD_LIBRARY_PATH is being overwritten, if that is what is happening.
Does anyone knows what's going on here?
Assuming gnome-terminal, I bet if you check "Run command as login shell" in Edit->Profiles->Edit->Title and Command, you'll get what you want.
Btw, LD_LIBRARY_PATH is generally not what you want. Unless you are quite careful, it can break the runtime execution of *all* commands. It is only useful to temporarily override the default path, or overcome the shortcomings of a pre-built proprietary binary. If you use LD_RUN_PATH instead, the path will be added to the binary's runtime path and will execute correctly without any env vars.
Why LD_LIBRARY_PATH is bad: http://xahlee.org/UnixResource_dir/_/ldpath.html
On Friday 06 July 2007, Garrick Staples wrote:
Why LD_LIBRARY_PATH is bad: http://xahlee.org/UnixResource_dir/_/ldpath.html
Not argueing against you here, but "...is prepended to the existing list of compiled-in loader paths for a given executable, and any system default..." from the link above isn't quite true on linux. rpath'ed stuff in the binary is searched before even LD_LIBRARY_PATH.
/Peter
-
Garrick Staples -
Jean Figarella -
joseph tacuyan -
Peter Kjellstrom