Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 1 ■ SAVING YOURSELF EFFORT1-12. Subversion: Dividing RepositoriesYou can keep going for a long time with the basic stuff with version control—as long as you’reremembering to commit all your changes, you’re fine. However, eventually you may need to messaround a bit with your repositories. Dividing, branching, and merging repositories are all things thatmay be necessary at some point and are straightforward with Subversion.So, you’ve decided that your single repository would be better off as two repositories. Maybe youwant to divide the config files from your scripts or from your notes. Before you start, make sure allworking changes are committed (or you’ll lose them when tidying up afterward) and that no one else isgoing to commit to the repository while you’re moving things around.To get a list of the directories in the repository and decide what to move, type the following:svn list file:///path/to/repositoryThen use this to get a dump of the repository (which may take a little while if you have a largerepository):svnadmin dump /path/to/repos > repos.dump■ Note Although svn will use http:// or file:// repositories, svnadmin takes only a plain path. So, you can’tuse it on a repository that you have only remote access to. You have to be logged in on the machine where therepository actually lives.Next, create the directory for your new repository:svnadmin create /path/to/newreposThe tool svndumpfilter allows you to choose a particular directory or directories. The command youwant is as follows:cat repos.dump | svndumpfilter include testdir | svnadmin load newreposThis pipes the old repository through svndumpfilter, tells the filter to include only the testdirdirectory, and then loads it into the new repository. (You can specify multiple directories if required.)All that’s left to do after this is to tidy up. If /local/checkout/testdir is where your existing workingcopy of testdir is living, use this:rm repos.dumpcd /local/checkout/svn delete testdirsvn commit -m "Deleting testdir from repository"svn checkout /path/to/newrepos/testdir testdirThis deletes the dumpfile, deletes the migrated directory from the old repository, and checks aworking copy out from the new repository.14Download at WoweBook.Com
CHAPTER 1 ■ SAVING YOURSELF EFFORT■ Note Unfortunately, there’s no way in Subversion to remove a directory from the database altogether, in otherwords, including all of its change history; this recipe just deletes it from this point in time, with all the pastinformation still kept. If you want to erase it altogether, you’ll have to use svndumpfilter exclude to create anew repository without the unwanted directory. This code will do that:svnadmin create /path/to/new_main_reposcat repos.dump | svndumpfilter exclude testdir | svnadmin load new_main_reposAfter you’ve checked your new main repository, you can delete the old one altogether and then check everythingout again from the new one.1-13. Subversion: Branching RepositoriesThe canonical situation for coders where you’d want to branch is when you want to create a dev branchof a project so that the main fork can be the stable code. (Or vice versa.) For sysadmin purposes, it mightbe useful to branch your config file tree when you upgrade some machines to a different version of yourdistro—so you can also merge across changes from the main version when they apply and then mergethe whole branch back in when you upgrade the other machines.To create a new branch, you need to make a copy of the main project:svn copy /path/to/repos/proj/trunk /path/to/repos/proj/branchNow check out that new directory to start working on the branch, and that’s it:cd my_branch_dirsvn checkout proj/branchIn due course, you’ll probably want to merge the changes back into the main tree (for example,when all your machines have been upgraded). This is going to be a little more complicated, becausechances are, you’ve made a few changes to the stable branch as well, and it may not be possible toautomatically merge them all.To merge changes from the trunk back to your branch, use this:cd my_branch_dirsvn merge /path/to/repos/proj/trunkCheck for conflicts with svn status, resolve them if necessary, run any appropriate tests (forexample, config file syntax checkers) to check for conflicts, and then commit the changes as usual.To merge your branch back into the trunk, first check out a clean copy of the trunk. Then (from thatchecked-out directory), run this:svn merge --reintegrate /path/to/repos/proj/branch15Download 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 33: 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 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?