![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Linux Support Linux - Operating Systems and Applications Support |
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Jan 2008
Posts: 20
OS: fedora8
|
Environmental Variables
How to set environment variables on RHEL 4.
I have configured Apache and Tomcat on my RHEL 4 machine.As per their instructions i have created some environment variabls in .bashrc file after created those variables both apache and tomcat working fine.When i logout and login the system it's ok there is no problem on both apache and tomcat whenever i restart the system both are not working again it was showing error messages. pls help |
|
|
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
|
#2 (permalink) |
|
Registered User
Join Date: Oct 2007
Location: Littleton, Colorado USA
Posts: 470
OS: xp 64 sp2 Fedora Core 8 (vmware xp core 8 x32) Minix
|
Re: Environmental Variables
You might put the environment variables into a file, then run the "source <file>'. Bash uses the source command as does the C-shell. I think for the sh-shell, the same thing is done with ". <file>". (It needs the dot). This is the ONLY way that you can set environment variables in the current running shell, since if you spawn a shell to run the <file>, the child's environment wouldn't set the parents. (Can't teach an old dog new tricks).
I think the real problem is which .bashrc's are being read by a login shell and later spawned shells. It sounds like from your description that the login shell is not executing the correct bashrc. Also Selinux could be undoing your bashrc's. I've heard that it can do that. Look at the "restorecon" command. I turn off Selinux. I have been too lazy to learn its in and outs. And it seems to get in the way. |
|
|
|
![]() |
| Thread Tools | |
|
|