Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 1 ■ SAVING YOURSELF EFFORTFigure 1-2. The database setup page for your second wiki. Note the changed database name.You need to use a separate database to keep your two wikis separate, so change the field with thedatabase name. You’ll also need to set the database username and password. If the user doesn’t yet existor doesn’t have database-creation permissions within your MySQL setup, you’ll need to provide thename and password for a MySQL user (possibly root) who does.Once the setup is finished, if it has all gone well, you should see an “Installation success” message.After this, you should move /new/wiki/config/LocalSettings.php to /new/wiki/, delete the /new/wiki/config/ directory, and make sure that other users cannot read the settings file:chmod og-rw /new/wiki/LocalSettings.php6Download at WoweBook.Com
CHAPTER 1 ■ SAVING YOURSELF EFFORT■ Note MediaWiki’s “Installation success” message may tell you to move LocalSettings.php to/etc/mediawiki. Ignore this!1-5. Scripting: Setting the Display StyleContrary to many an argument on the Internet, style choices (tabs or spaces, line lengths, cuddled elses,or whatever) don’t really matter. The important thing is to make a decision and stick with it.It is, however, a good idea to set all your text editors on all your machines (see Chapter 3 forcentralization tips) to have sub-80-character lines. For vim, add the following line to your ~/.vimrc:set tw=78For emacs, add this in ~/.emacs:(setq-default fill-column 78)For nano, add this in ~/.nanorc:set fill 78This is because someone else will have to read that script after you, or you might wind up reading iton a text console that doesn’t have your proper setup. In those cases, the lines won’t wrap properly, andyou will cry. Keep it short. Use \ in bash to break up a line; with Perl, newlines are ignored since ; ends astatement, so break the line wherever you want.1-6. Dealing with Variables in PerlWhen you need a quick-fix script, Perl and bash are fantastic tools. They’re comprehensive, they’reflexible, and they can be tied together with other system tools. Having said that, while you can do a lotwith bash, you probably shouldn’t unless there’s a very good reason, such as a need for major portability,in which case you need to consider a number of other factors—check out Beginning Portable ShellScripting by Peter Seebach (Apress, 2008). If the task is going to take more than about ten lines or requiremuch more than stringing a series of shell commands together, it’s best to use Perl (or your preferredscripting alternative).The other issue to bear in mind is whether you need a script at all. Really large projects might bebetter in another language; see recipe 1-16 later in this chapter for making sure that you’re notreinventing the wheel.Anyway, scripting languages may be great tools for getting something working in a hurry, but theirvery greatness can lead to cutting corners in the name of speed. Then six months down the line your“quick hack” is still there, has developed add-ons and a bug or two, and you can’t remember what onEarth you were thinking when you wrote it. As with the documentation mentioned earlier in this chapter(recipes 1-1 through 1-4), spending a little extra time now can save you a lot of time and mental energylater.7Download 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: CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 41 and 42: C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 77 and 78:
CHAPTER 2 ■ CENTRALIZING YOUR NET
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:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
C H A P T E R 5■ ■ ■Working w
Page 141 and 142:
CHAPTER 5 ■ WORKING WITH FILESYST
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
C H A P T E R 6■ ■ ■Securing
Page 157 and 158:
CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
CHAPTER 7 ■ WORKING WITH APACHEOn
Page 181 and 182:
CHAPTER 7 ■ WORKING WITH APACHEdi
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 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
CHAPTER 9 ■ WORKING WITH TEXT IN
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
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 227 and 228:
Page 229 and 230:
Page 231 and 232:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?