Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

■ CONTENTSAbout the Technical Reviewer■Sean Purdy first encountered a computer when he was seven, his uncle’s Apple ][. He learned toprogram on the BBC Microcomputer, like so many protogeeks did in the 1980s. During his electronicsdegree, he was exposed to SunOS, which kick-started a lifelong interest in Unix-like operating systems.Linux came along in the mid-1990s in the form of Slackware, about the same time he finally got hishands on a 386sx machine capable of running it. Since then, he has been trying to run Linux oneverything and anything–games consoles, PDAs, and tiny laptops. The toaster is starting to worrySean has worked for several ISPs and technology companies, with almost 15 years of experience ofLinux, FreeBSD, and Solaris. He now works as a systems guy for Consolidated Independent, deliveringmusic and video content to iTunes, Amazon, and other digital music services.Sean lives in London with two cats and a person.xiiDownload at WoweBook.Com
■ CONTENTSAcknowledgmentsMany thanks to the various people from Apress who worked on this book with me: Frank Pohlmann,who handled the technical editing and who helped me work out the original plan for the book; KimWimpsett, who patiently copyedited out my assorted verbal tics and U.K. English; and Kylie Johnston,who took over project management from Sofia Marchant and who navigated everything through thepublication process with impressive speed and good humor. I was particularly happy to have Sean Purdyas technical reviewer, because he’s been a good friend of mine for a long time now–thank you for allthe painstaking checking and electronic red pen, Sean! The input from them all has made this a muchbetter book.I’ve been fortunate in my career as a sysadmin to have managers who’ve been happy to let meoperate freely and who have been very encouraging. In particular, Anne Wilson, the IT manager when Iwas working at St Hilda’s College, Oxford, was incredibly supportive and helpful at a time when I wasvery much just starting out and doing a lot of learning on the job (read: making numerous mistakes). I’vealso learned a great deal through the various IT-related problems that my colleagues in the AstrophysicsGroup at Imperial College brought to me when I was working there, and I enjoyed my time there.On a more personal level, I want to thank my parents. They’ve always been incredibly supportive ofme, and they’ve already assured me that they will be reading this book despite not knowing anything atall about Linux!.Finally, gratitude and love as ever to my partners, Pete and doop, and to my best friend, Marna, whohave patiently put up with my complaints; made encouraging noises at appropriate points; provided tea,rocket-fuel coffee, and/or chocolate when necessary (my burgeoning caffeine habit is entirely theirfault!); and in general continued to be the awesome individuals that they are, even when 10,000 milesand quite a few time zones away. Special thanks to Pete for allowing me to mess about with his machinesin the name of science testing.xiiiDownload 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: ■ CONTENTSAbout the Author■Juli
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 41 and 42: C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 65 and 66:
CHAPTER 2 ■ CENTRALIZING YOUR NET
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:
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

Create successful ePaper yourself

Delete template?

Save as template?