Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Yesterday, I was trying to work out why a web application we developed had stopped working on a client's RHEL4 box. As well as our app being broken, apache wouldn't start up on reboot as it had done previously.
The problem was that a recent httpd rpm update had corrupted the system.
running /usr/local/apache2/bin/apachectl start
allowed apache to start. Our app started ok aswell but some of its functionality is still not working.
It looked like the httpd init script in /etc/init.d/ had references to
/usr/sbin/apachectl and /usr/sbin/httpd, so I changed them to point to
/usr/local/apache2/bin/apachectl and /usr/local/apache2/bin/httpd. Now apache is starting on reboot, but some of the apps functionality is still broken. (Its a java app, running on tomcat. Does anyone have any clue as to what might have been corrupted after an update that would cause problems?)
The person who installed the apache on the server didn't remove the httpd rpm before doing so.
Whenever I've installed apache in the past, I've always removed the pre-installed httpd rpm and its dependencies without really knowing why except that I imagined that conflicts could happen. Could someone explain the how and why conflicts do potentially occur?
Also, after an automatic update, is a there a quick way of seeing which files have been modified as a result of the update, other than using 'find' to locate files that have been modified within a certain timeframe?
Unfortunately I don't have access to the server today.
Also, I ended up removing the httpd package and its dependencies to see if that would help, and I noticed that /etc/httpd/conf/httpd.conf .rpmsave was created, so I imagine that any other .rpmsave files that are knocking about are a result of the package removal, rather than the package update. Am I right in thinking that?
I don't know. I've always used the preinstalled packages unless there is a specific thing I need to run. Perhaps the preinstalled packages don't support something you want or RHEL4 is apache 1.3.x and you need something in 2.0.x?