Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFSobjectclass ( 1.2.3.2 NAME 'localDesktop' SUP top AUXILIARYDESC 'Desktop objectclass'MAY ( localUser ))First, then, let’s talk about that warning at the top. Every object in an LDAP schema has to have anobject identifier (OID). All the ones in the schemas you’ve already grabbed will have been officiallyallocated; you have the choice, when creating your own, of contacting ICANN or another registryauthority to get a number range or of just making one up that doesn’t clash with anything you’re usinglocally. The former is obviously the correct way to do it! But it may not always be worth the hassle if youwill use this only locally. If you do get an OID allocated, you can create anything you like underneath it.So, if you did get 1.2.3, you could also use 1.2.3.1, 1.2.3.2.2.3.1, or anything else beginning 1.2.3.■ Note Check out http://www.alvestrand.no/objectid/ to see the tree of existing OIDs.So, the rest of that first line gives the attribute a name (no spaces). DESC is a human-readabledescription string. EQUALITY defines how the attribute will behave in a search; this uses IA5 strings andignores case when searching. SYNTAX defines the data type:; this one is an IA5 string.SUP indicates that the object class has a parent. In this case, the parent is 'top', which is a specialclass that is the highest level of all object classes. AUXILIARY is its structural type and means that this classcan be used within an entry but can’t form an entry all by itself (so you can’t have an object that is just alocalDesktop).MAY( icUser ) states that an object of this type may (but does not have to) have the icUser attributethat we defined earlier.You’ll then need to add this line to your /etc/ldap/slapd.conf file, after the other schema lines:include/etc/ldap/schema/local.schemaand restart slapd.Of course, just adding the schema doesn’t automatically make any of your objects be of the newclass or have the new attribute. You’ll need to set up an LDIF file for that, with an entry like this for eachmachine you want to change:dn: cn=client1,ou=Hosts,dc=example,dc=comchangetype: modifyadd: objectClassobjectClass: icDesktop-add: icUsericUser: user1Leave a blank line in the file between each host that you’re changing, with no blank lines around the– line (this separates modifications to be done on the same host). Then use ldapmodify -f file.ldif tomake the changes. Remember to authenticate as the correct user first.58Download at WoweBook.Com
CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFS2-14. Using NFS and automountA basic NFS shared directory is usually very straightforward to set up. To share the /local/ directory toany other machine in the 10.1.0.* subnet, edit the /etc/exports file on the machine that the sourcedrive is on (let’s call it server1):/local 10.1.0.*rwThen restart the NFS server (/etc/init.d/nfs-kernel-server restart). Next mount the drive fromany other machine in that subnet, on that machine’s /mnt directory, with this:mount server1:/local /mntTo set this up to mount automatically on boot, add it to /etc/fstab:/mnt server1:/local nfs defaults 0 2However, a more flexible approach than manual mounting is to use automount. With this, drives areautomatically mounted on request, rather than being mounted all the time (as with the previous setup).You can set up a central home disk on your server and have that automounted on request. Theadvantages to a central home disk are fairly obvious: anyone can work on any machine, and backups aremade easier. If it’s automounted, then it won’t affect the bootup procedure if there’s a problem of somesort with the server.Install the package on the client:apt-get install autofsThen edit the /etc/auto.master file on the client to have this line:/home -rw server1:/export/homeRestart autofs, and then type cd /mnt/server. The directory should appear and list correctly.Automounting really comes into its own if you get your automount maps from your LDAP server.Partly, this has the usual centralization advantage that if a mapping changes, you need to change it onlyonce, in one place, not on all your machines. But it also means that you can set up home directorymappings individually (per directory) rather than the home directory as a whole, but without having tohave unwieldy swathes of mappings.Install the autofs-ldap package, and edit your /etc/auto.master file to read as follows:/homeldap:automountMap=auto.home,dc=ph,dc=ic,dc=ac,dc=ukThen log into the LDAP server. You’ll need to add one parent map entry, for the directory map as awhole, and then individual per-user maps. The LDIF file here describes the parent map and one usermap:dn: ou=auto.home,dc=example,dc=comobjectClass: topobjectClass: automountMapou: auto.home59Download 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:
CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 27 and 28: 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: 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 115 and 116: C H A P T E R 4■ ■ ■Taking Ba
Page 117 and 118: CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 129 and 130:
CHAPTER 4 ■ TAKING BACKUPS AND MA
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?