Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFSThis modify_file would changes the user’s login shell to bash:dn: uid=jkemp,ou=People,dc=example,dc=comchangetype: modifyreplace: loginShellloginShell: /bin/bashThe changetype is specified as modify, and the field to replace is given before the replacement valueis given on the last line.This file would add an emailAddress field to the specified user, with the value given in the last line:dn: uid=jkemp,ou=People,dc=example,dc=comchangetype: addadd: emailAddressemailAddress: user@example.comNote the different changetype. You’re adding a field rather than modifying it, but again you specifythe field to add and then the value to add in much the same way as the replacement was specified in theprevious file.ldapdeleteFinally, use ldapdelete to delete an existing entry. All you need to specify for this is the DN of the entryyou want to delete:ldapdelete "cn=isis,ou=Hosts,dc=example,dc=com"You can also use ldapdelete -f file, where file contains a list of DNs in the same format, one perline, all of which will be deleted in turn.2-8. Setting Up a Slave LDAP ServerYou can run with just a single LDAP server, but it’s a far better idea to have at least two. That way, first,you can spread the request load if need be, and second, you have a backup so that if something goeswrong with your master server, users can still access the LDAP database (and thus log on and work!)while you’re fixing the problem.You can set up a slave LDAP server fairly easily. The slave server will handle any requests forinformation but will automatically pass any change requests to the master server. This means that thedatabase has to be replicated in only one direction and avoids the possibility of conflicting changesbeing made on different servers.For authentication, we’ll use rep_adm as the replication admin user (which will need to operateautomatically) and ldapadm as the regular interactive admin user (which therefore authenticates with apassword).■ Note This used to be handled by slurpd, but this has been deprecated now in favor of syncrepl.42Download at WoweBook.Com
CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFSIn the /etc/ldap/slapd.conf file on your master server, add this section in the Specific Directivesfor database #1 section of the file:overlay syncprovsyncprov-checkpoint 100 10syncprov-sessionlog 200index objectClass,entryUUID eqThis will perform a checkpoint every 100 operations or 10 minutes (the second line) and will record200 lines of session log (the third line). The final line sets up indexing. The session log (which is used forLDAP Sync searches) searches on entryUUID, so setting an index on this attribute speeds up thesesearches.Set up your slave server with the same basic configuration as the master, but instead of the syncprovsection used earlier for the master, use these lines:access to *by dn="uid=ldapadm,ou=people,dc=example, dc=com" writeby dn="uid=rep_adm,ou=people,dc=example, dc=com" writeby * readindex objectClass,entryUUID eqsyncrepl rid=450provider=ldaps://ldapserver.example.com:636type=refreshAndPersistsearchbase="dc=example,dc=com"schemachecking=offbindmethod=saslsaslmech=GSSAPIbinddn="uid=rep_adm,ou=people,dc=example,dc=com"Here both ldapadm and rep_adm have access to write to the database.■ Note If your master server doesn’t have universal read access (which is the setup used in recipes 2-3 and 2-4and so what I assume here), you’ll need to give read access to rep_adm on the master server:access to *by dn="uid=rep_adm,ou=people,dc=example, dc=com" readThe syncrepl section will perform a synchronization check on the whole database once every fourhours (set by the interval line). The provider is the main LDAP server. The refreshAndPersist type meansthat the slave server will continue listening for any changes, which will be updated immediately (theless-useful alternative is refreshOnly, which just checks at the given interval and then signs off, so anychanges won’t be replicated until the next check. If you use this, you’ll need to set an interval value—seethe LDAP syncrepl docs).43Download 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 41 and 42: C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 61: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 83 and 84: C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86: CHAPTER 3 ■ MONITORING AND UPDATI
Page 113 and 114:
CHAPTER 3 ■ MONITORING AND UPDATI
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?