Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 12 ■ MANAGING TIME AND PEOPLEServerAdmin admin@example.comServerName www.example.comDocumentRoot /local/www/htmlOptions +IncludesAddType text/html .shtmlAddOutputFilter INCLUDES .shtmlOptions FollowSymLinks IncludesAllowOverride NoneOptions Indexes +Includes FollowSymLinksAllowOverride FileInfo AuthConfig OptionsOrder allow,denyAllow from allInclude /etc/request-tracker3.6/apache2-modperl2.confSSLEngine onSSLCertificateFile /etc/apache2/ssl/apache.pemThe important line is the one that references the RT include file! Restart Apache2 (with/etc/init.d/apache2 force-reload), and you should be able to access RT via HTTPS.You can also integrate RT with Kerberos to use Kerberos sign-on to access the RT web pages.■ Note This doesn’t strictly form part of the single-sign-on process; your users will have to enter their passwords.But it does avoid the need to remember a separate password.Create an apache2 keytab via krbadm, and add this section in the section of yourApache config:# KerberizationAuthType KerberosV5AuthName "Request Tracker"KrbAuthRealm EXAMPLE.COMKrb5Keytab /etc/apache2/apache2.keytab # or appropriate location242Download at WoweBook.Com
CHAPTER 12 ■ MANAGING TIME AND PEOPLERequire valid-user# We don't use kerberos auth for the "noauth" areas of RT - these are the# areas that run outgoing mail and other similar things.Order allow,denyAllow from allSatisfy anyOrder allow,denyAllow from allSatisfy anyNext, you need to edit RT_SiteConfig.pm to add these lines:Set($WebExternalAuto , 1);Set($WebExternalAuth , 1);Reload Apache2 (/etc/init.d/apache2 force-reload) to implement the changes, and then trylogging on with your Kerberos password.■ Note The $WebExternalAuto line also sets RT up such that if a new user logs in or sends a request by e-mail,a user account is automatically added. This saves you time!12-6. Getting Big Projects DoneAs discussed in recipe 12-1, sysadmin work by its nature tends to be interrupt-driven. As well assometimes making it hard to keep track of, this can also mean that it’s hard (or seems hard) to find timeto sit down and work on larger projects, such as replacing servers, introducing new pieces of software,or doing web site revamps if that’s part of your job (as it may be in a smaller company), and so on.There are a couple of solutions to this. Probably the first thing to do is to make sure that only theprojects that really need to be large undertakings are in fact time-consuming. Server replacement, forexample, such as when acquiring a new desktop machine, should be straightforward and automated asfar as possible. (Of course, setting up the automation itself may come under the heading of a largeproject!).In general, make sure that you’re being as time-efficient as possible. The general rule is that by thesecond time you do something, you should be looking at automating it. Some issues may come up onlyonce; it’s rare for something to come up only twice. It’s much more likely that it’ll return again, at whichpoint any time taken in automating it becomes valuable.You should seek to minimize the amount of effort it takes just to keep things running smoothly. Bycentralizing your systems (see Chapters 2 and 3), keeping good notes and records (see Chapter 1), andkeeping your systems secure (see Chapter 6), you should aim to have as much as possible of your setup243Download 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:
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:
CHAPTER 9 ■ WORKING WITH TEXT IN
Page 211 and 212: 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 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 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 261: CHAPTER 12 ■ MANAGING TIME AND PE
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?