Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Trim down size of Apache server
- Thread starter KevinAr18
- Start date
I don't know if this helps or not, but I recall seeing an entire chapter on slimming down Apache and improving Apache performace in the "Apache Server 2 Bible" book.
---------------------------------------
If someone's post was helpful to you, please click the box "Click here to mark this post as a helpful or expert post".
---------------------------------------
If someone's post was helpful to you, please click the box "Click here to mark this post as a helpful or expert post".
- Thread starter
- #3
Well getting a book just for this purpose doesn't seen practical. Besides, someone who I can actually talk to who knows what they are doing would be much more helpful.
For example, what are all the .h files for? Can they be removed? questions like that.... Does anyone here know files I could remove and would be willing to talk either on AIM or email or something?
For example, what are all the .h files for? Can they be removed? questions like that.... Does anyone here know files I could remove and would be willing to talk either on AIM or email or something?
The .htaccess files are for overriding settings found in previous directives in the httpd.conf file on a per-directory basis. If you set...
<Directory />
AllowOverride None
</Directory>
... in the global config, then .htaccess files won't be used anymore (unless activated elsewhere) and you can delete them.
"Besides, someone who I can actually talk to who knows what they are doing would be much more helpful" -->
Your talking to someone who knows what they are doing, but if you have a million general questions on Apache your better off reading a book or some HOWTO's and then asking specific questions that you are having trouble with afterwards.
If you have a specific question, I'll do my best to answer it, or hopefully someone else will. I'm not an Apache expert by any means, but I can answer a lot of questions about it. I learned pretty much everything I know about Apache from reading the book I mentioned above.
Here's one thing you can try. Run httpd -l to see what modules are compiled into Apache and then remove the ones you don't need using the configure script from the Apache source directory. This is probably the single best thing you can do to clean Apache up.
ChrisP ---------------------------------------
If someone's post was helpful to you, please click the box "Click here to mark this post as a helpful or expert post".
<Directory />
AllowOverride None
</Directory>
... in the global config, then .htaccess files won't be used anymore (unless activated elsewhere) and you can delete them.
"Besides, someone who I can actually talk to who knows what they are doing would be much more helpful" -->
Your talking to someone who knows what they are doing, but if you have a million general questions on Apache your better off reading a book or some HOWTO's and then asking specific questions that you are having trouble with afterwards.
If you have a specific question, I'll do my best to answer it, or hopefully someone else will. I'm not an Apache expert by any means, but I can answer a lot of questions about it. I learned pretty much everything I know about Apache from reading the book I mentioned above.
Here's one thing you can try. Run httpd -l to see what modules are compiled into Apache and then remove the ones you don't need using the configure script from the Apache source directory. This is probably the single best thing you can do to clean Apache up.
ChrisP ---------------------------------------
If someone's post was helpful to you, please click the box "Click here to mark this post as a helpful or expert post".
- Thread starter
- #5
I would be very careful about "trimming down" Apache in this manner. You might remove something you don't seem to need, only to find out weeks later that it was necessary at one critical point.
The better way to approach it is to uninstall Apache, and reinstall with the minimal configuration you think you will need, compiling it from scratch. I know this is a pain, but it's the only way to get a clean system.
If you are using Linux, this can be a bit of a problem, because different Linux distributions each have their own layout for Apache files, and you will have to make sure those are cleaned out before recompiling Apache.
I personally tend to configure a very minimal Linux or FreeBSD Unix box, and then install Apache/PHP/mod_perl from source code. This usually results in just a few megs of data being added to the system. If hard drive space is an issue, I recommend using Slackware or Debian Linux, if you don't want FreeBSD. -------------------------------------------
"Now, this might cause some discomfort..."
(
The better way to approach it is to uninstall Apache, and reinstall with the minimal configuration you think you will need, compiling it from scratch. I know this is a pain, but it's the only way to get a clean system.
If you are using Linux, this can be a bit of a problem, because different Linux distributions each have their own layout for Apache files, and you will have to make sure those are cleaned out before recompiling Apache.
I personally tend to configure a very minimal Linux or FreeBSD Unix box, and then install Apache/PHP/mod_perl from source code. This usually results in just a few megs of data being added to the system. If hard drive space is an issue, I recommend using Slackware or Debian Linux, if you don't want FreeBSD. -------------------------------------------
"Now, this might cause some discomfort..."
(
- Thread starter
- #8
- Status