专家级shell脚本编程（2009年版）：全面指南

需积分: 16 123 浏览量更新于2024-07-29 收藏 1.39MB PDF 举报

《Apress Expert Shell Scripting (January 2009)》是一本由Ron Peters撰写的专著，专注于高级Shell脚本编程。该书是Apress出版社于2009年出版的专业技术书籍，版权受到严格的保护，未经版权所有者和出版商事先书面许可，不得任何形式复制或传播，包括打印、录音以及通过任何信息存储或检索系统。本书的主要内容涵盖了Shell脚本的高级技巧和实践，适合那些希望深入理解并提升Shell编程能力的读者。作者Ron Peters以其丰富的经验，带领读者探索Shell脚本在自动化任务、系统管理和脚本设计中的应用，包括但不限于文件操作、管道、函数、错误处理、脚本调试等核心主题。书中可能还探讨了当时的最新技术和最佳实践，如bash shell的高级特性，以及如何利用它们来提高生产效率。《Apress Expert Shell Scripting》的编写采用了严谨的编审流程，由Frank Pohlmann担任主编辑，Brian Culp担任技术审稿人，确保了内容的专业性和准确性。编辑团队包括多位业内专家，如Clay Andres、Steve Anglin等，他们共同确保了书中的内容既具有理论深度又易于理解，适合不同技术水平的学习者阅读。本书不仅提供理论知识，还包括实践案例和示例，帮助读者通过实际操作掌握Shell脚本的高级技术。此外，版权信息也包含了印刷及电子版本的ISBN号，以及项目管理、校对和排版团队的详细名单，体现了出版社对作品品质的重视。《Apress Expert Shell Scripting》是一本不可或缺的资源，对于任何希望在Shell编程领域深化专业知识和技能的开发者或系统管理员来说，它是一份宝贵的参考资料和实战指南。通过阅读这本书，读者可以提升自己的Shell编程水平，更好地应对现代IT环境中的自动化和系统管理挑战。

xxi

Introduction

I learned the basics of programming when I was in school; I learned how to shell-script by

example.

I’ve met and worked with many system administrators and other *NIX folks, each of

whom has their own bag of tricks when it comes to managing a system, interacting with

their environment, or coding a script. It’s always very useful to have conversations and

interact with people like this because you invariably gain some tidbits that you can

throw into your own collection of tricks. I decided to collect all the useful shell-scripting

and interaction techniques I have learned through the years and combine them into one

beneficial reference guide. In fact, I used some of my own notes about those techniques

while writing this book. Since I haven’t memorized everything present in this book, I

would periodically look up items when I was working on various tasks. I want this book

to be the beginning of a higher-level reference library that can be added to and can grow

continually.

You might be aware of the large number of shell-scripting books and online resources

aiding in the mastery of shell scripting. Many are excellent and cover a wide range of topics.

The main purpose of this book is to combine some of the most unique tools, code snippets,

and scripts that go beyond the level of basic scripts. I wanted to create a cookbook of sorts—

lesser-known recipes and fairly advanced algorithms that have proved useful to me.

I have included scripts you can use as is, and sample scripts illustrating a specific algo-

rithm. I also demonstrate a few complex commands that may be useful on the command

line. I have tried to tailor the scripts to be useful at multiple levels. Most times, however,

there is little or no error-checking since that is not necessarily the point of a specific script.

You must be prepared to make modifications to fit your local environment.

How This Book Came About

My friend Brian Culp and I have worked together as UNIX system administrators for many

years. Periodically, Brian or I will be working on some script and run into a problem. One

of us will stop, walk over to the other, and say something like, “Do you have any code that

does X?” The answer may be no, in which case we’ll launch into a discussion on how we

might tackle the problem, or come up with a few different solutions. However, many times

it might be something like, “Hmm, yeah, I think I remember doing something like that in

a script that does X on system Y. Let me look for a minute.” A few carefully chosen grep

commands, and the solution is at hand.

xxii

■INTRODUCTION

Although finding the solution we want is great, it’s not the most efficient use of our

time. To go from having a place to store and organize all of our (and, of course, other

programmers’) gems and having them in a heavily documented form, to writing a book

on the subject was only a short step. Even though it is possible to search online references

quickly for specific code, there were many occasions when I just wanted to pull a book off

my shelf. It’s not always obvious what to search for when you have a specific itch that

needs scratching, so you’re not sure exactly to what search for online.

This is to some extent an expression of my own limitations: my family and friends think

I’m a computer guru, but rest assured, I know better. There are many programmers out

there who are much more adept at shell coding than I am. I mainly intended to collect,

order, and explain code that I have found to be highly useful in my professional experi-

ence as a system administrator, and share that information with others.

Who Should Read This Book

The book is meant for the intermediate shell coder up to the advanced shell-code hacker,

because I don’t explain many basic programming structures. If you’re looking for that

type of book, you should look to the resources mentioned in Appendix C.

This is not to say that the beginner won’t find this book useful; it may work well as a supple-

mentary reference to a more traditional shell-scripting training guide. But there is a difference

between learning English as a second language and learning how to apply sarcasm. This book

is like sarcasm in that example; it assumes some basic shell-code literacy.

I go into great detail about how and why the scripts were written in their present form,

and I include some explanation of how to avoid certain problems. Much of my learning

came from sources heavy in obfuscation and light on clarity, so I tried to be as explicit as

possible, and favored explaining too much rather than too little. You can think of many

chapters I included as shell scripts with extremely detailed commentary.

The book is divided into three parts: “Basic Scripting Techniques,” “System Interaction

and Advanced Techniques,” and “Useful Scripts.” Most chapters serve as stand-alone

discussions, although they may refer to other chapters on some minor points.

Issues and Ideas

I have made every effort to test the code that I included in this book to validate that it

works. With a project of this size, however, even with the number of eyes that have

reviewed it, there may be mistakes. I would like to know about the mistakes as well as, and

more importantly, any other ideas and scripts that could be used for future revisions of

this book. Please drop me a note at rbpeters@peterro.com.

■ ■ ■

CHAPTER 1

Shell Script Debugging

Even though this book isn’t a “how to script” manual, some concepts that are funda-

mental to writing successful scripts should be discussed. Debugging is one of them.

Debugging code is a significant part of writing code. No matter how disciplined you are

or how skilled you become at coding, you will have bugs in your code, in the form of either

syntax or logic errors. The syntactical problems tend to be simpler to resolve since many

times they show up when the code throws an error when it is run. The logical bugs, on the

other hand, may be more difficult to track down since the code may run without error, but

the resulting output does not match the design of the program. The more complex your

code becomes as your skill increases, the more difficult these types of problems will be to

detect.

Since writing bug-free code is nearly impossible, you need a few techniques up your

sleeve that will help you finish, diagnose, repair, and clean up your code. This chapter pre-

sents a few ways to debug code that I have used consistently and that help me extract

details from the inner workings of my scripts. These techniques validate that the code is

living up to my expectations and demonstrate where the code needs more work to per-

form the intended task.

Shell Trace Options

The first technique—using the set command—is the simplest to implement and can give

you great amounts of detail about how the logic is progressing and the values of variables

internal to your script. Using the set command is really just using shell options to display

verbose output when the script is running. One of the functions of the set command is to

turn on and off the various options that are available in the shell. In this case, the option

being set is -x, or xtrace. This is where the running script will, in addition to any normal

output, display the expanded commands and variables of a given line of code before the

code is run. With this increased output, you can easily view what is happening in the run-

ning script and possibly determine where your problem lies.

When you put the instruction set -x into your script, each of the commands that exe-

cute after that set instruction will be displayed, together with any arguments that were

supplied to the command, including variables and their values. Each line of output will be

剩余281页未读，继续阅读

guangquanz

粉丝: 0
资源: 55

专家级shell脚本编程（2009年版）：全面指南

《Apress.Pro.Expression.Blend.4》：精通微软WPF与Silverlight开发的全面指南

精通Web前端：Apress.Pro JavaScript实战指南

《ExpertShellScripting》：调试艺术与复杂代码挑战

Apress.Expert.Shell.Scripting

Apress.Expert.Indexing.in.Oracle.Database.11g.Jan.2012.pdf

Apress.Expert.Oracle.Database.11g.Administration.2009.rar

Apress.Expert.JavaScript

Apress.Expert.Android.2013

Apress.Practical.DWR.2.Projects.Expert's.Voice.in.Java.Jan.2008.pdf

Apress.Expert.SharePoint.2010.Practices

最新资源