Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 7 ■ WORKING WITH APACHE3. Set the parameter loadmodule, which will then be used when parsing theconfig file:apache2 -D loadmoduleSo, if your config file includes this:01 02 LoadModule my_other_module03 then my_other_module will be loaded only if the parameter is set. You canuse this for testing modules before adding them permanently by definingloadmodule in the config, or you can use it for testing anything else that youput within an appropriate IfDefine section. The IfDefine section can betemporary (that is, you can remove it after testing) to allow you to switchquickly backward and forward when testing a module or a section of config.When you’re happy, remove lines 01 and 03 to avoid the need for theparameter to be passed in.4. Get information about Apache:apache2 -lapache2 -Lapache2 -SThe first outputs a list of compiled modules so you can check which modulesare available and loaded already. The second gives a list of directives (such asthe SSL directives discussed in recipe 7-4) and where they apply. This can bereally useful for troubleshooting purposes. The third shows the VirtualHostsettings as constructed from the config file. Again, this can be useful whentroubleshooting to check which settings are being applied to whichVirtualHost and that nothing has been missed. Add this section to your configfile, and then run apache2 -S to take a look at the VirtualHost settings:ServerAdmin othersite_web@localhostDocumentRoot /var/www/myothersite/Options FollowSymLinks +IncludesAllowOverride NoneErrorLog /var/log/apache2/othersite_error.log7-2. Apache2: Dealing with ModulesApache2 is modular, which means there’s a core system and then a set of modules that you can includein the main system if you choose. Some of the modules are statically built, which means that they’rebuilt in when the server is compiled and can’t be removed without recompiling the server. Thesemodules can’t be loaded or unloaded on the fly. If you’re using the Apache2 package for your160Download at WoweBook.Com
CHAPTER 7 ■ WORKING WITH APACHEdistribution, you won’t have any control over which modules are built in like this. If you want a differentset of built-ins, you’ll need to recompile Apache2 yourself. As a rule, you shouldn’t need to do this;anything that’s missing from the built-in list can be installed dynamically (which I’ll describe in amoment). You’ll need to recompile if you want to disable any of the built-in modules, but avoid this ifpossible, since compiling your own software is far less maintainable than using your distro’s packagingsystem.To get a list of the built-in modules, use this command:apache2 -iDynamic shared objects (DSOs) are the other type of module. These exist separately from the mainbinary and can easily be loaded when the server starts or reloads. So, you can take them in and out asyou need. Again, your distro package will probably include a few of these modules, and separatepackages will be available for other modules.In general, a Fedora-type system will by default load most of the modules that are provided with theserver, whereas a Debian system will load only a few. You’ll need to choose to load the rest using thea2enmod tool, which I’m about to explain.With Debian, you’ll find all the module load information in the directory /etc/apache2/modsavailable/;this is also where the config files (when needed for a particular module) live, and you canedit the configuration here. To load a module, a symlink is created from /etc/apache2/modsenabled/modulename.loadto /etc/apache2/mods-available/modulename.load.> ls -l /etc/apache2/mods-enabled/…lrwxrwxrwx 1 root root 27 2009-07-14 14:20 php5.conf -> ../mods-available/php5.conflrwxrwxrwx 1 root root 27 2009-07-14 14:20 php5.load -> ../mods-available/php5.load...■ Note The lines in /etc/apache2/apache2.conf that handle this are as follows:Include /etc/apache2/mods-enabled/*.loadInclude /etc/apache2/mods-enabled/*.confEach modulename.conf file is usually a single line like this:LoadModule modulename /usr/lib/apache2/modules/modulename.soYou could, if you like this method of managing module configuration but are not using Debian, set up somethingsimilar yourself by manually creating these directories and the appropriate *.load and *.conf files and adding theinclude lines for both directories. Then remove the LoadModule lines and the module configuration from the main161Download at WoweBook.Com
Page 2:
Download at WoweBook.Com
Page 5 and 6:
Download at WoweBook.Comiii
Page 7 and 8:
Contents■About the Author .......
Page 9 and 10:
■ CONTENTS3-7. Writing a Nagios P
Page 11 and 12:
■ CONTENTS■Chapter 8: Using the
Page 13 and 14:
■ CONTENTSAbout the Author■Juli
Page 15 and 16:
■ CONTENTSAcknowledgmentsMany tha
Page 17 and 18:
■ CONTENTSIntroductionThis book i
Page 19 and 20:
■ INTRODUCTIONDownloading the Cod
Page 21 and 22:
C H A P T E R 1■ ■ ■Saving Yo
Page 23 and 24:
CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44:
CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86:
CHAPTER 3 ■ MONITORING AND UPDATI
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
C H A P T E R 4■ ■ ■Taking Ba
Page 117 and 118:
CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130: CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 139 and 140: C H A P T E R 5■ ■ ■Working w
Page 141 and 142: CHAPTER 5 ■ WORKING WITH FILESYST
Page 155 and 156: C H A P T E R 6■ ■ ■Securing
Page 157 and 158: CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 179: CHAPTER 7 ■ WORKING WITH APACHEOn
Page 183 and 184: CHAPTER 7 ■ WORKING WITH APACHE4.
Page 185 and 186: CHAPTER 7 ■ WORKING WITH APACHE
Page 187 and 188: CHAPTER 7 ■ WORKING WITH APACHEAl
Page 189 and 190: CHAPTER 7 ■ WORKING WITH APACHE
Page 191 and 192: C H A P T E R 8■ ■ ■Making Be
Page 193 and 194: CHAPTER 8 ■ USING THE COMMAND LIN
Page 207 and 208: CHAPTER 9 ■ WORKING WITH TEXT IN
Page 223 and 224: C H A P T E R 10■ ■ ■Things G
Page 225 and 226: CHAPTER 10 ■ THINGS GO IN, THINGS
Page 231 and 232:
CHAPTER 10 ■ THINGS GO IN, THINGS
Page 233 and 234:
C H A P T E R 11■ ■ ■Tracking
Page 235 and 236:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 237 and 238:
CHAPTER 11 ■ TRACKING DOWN BUGS01
Page 239 and 240:
CHAPTER 11 ■ TRACKING DOWN BUGS
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 247 and 248:
CHAPTER 11 ■ TRACKING DOWN BUGSAn
Page 249 and 250:
CHAPTER 11 ■ TRACKING DOWN BUGS#
Page 251 and 252:
C H A P T E R 12■ ■ ■Managing
Page 253 and 254:
CHAPTER 12 ■ MANAGING TIME AND PE
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
APPENDIX■ ■ ■Perl TipsSee rec
Page 269 and 270:
APPENDIX ■ PERL TIPS• Date::Par
Page 271 and 272:
APPENDIX ■ PERL TIPSPerl Syntax N
Page 273 and 274:
■ ■ ■Index■Symbols$CDPATH,
Page 275 and 276:
■ INDEXenscript option (printing)
Page 277 and 278:
■ INDEX■NNagiosadding hosts to,
Page 279 and 280:
■ INDEXsyslogcentralized logging
Page 281 and 282:
Download at WoweBook.Com
show all

Linux System Administration Recipes A Problem-Solution Approach

Create successful ePaper yourself

Delete template?

Save as template?