Shell脚本专家指南：进阶编程技巧

4星 · 超过85%的资源需积分: 16 146 浏览量更新于2024-07-30 27 收藏 1.39MB PDF 举报

"这是一本关于shell编程进阶的专家指南，由Ron Peters撰写，版权归属2009年的Ron Peters。书中深入探讨了shell脚本的高级技巧和应用，旨在帮助读者成为shell脚本编写的专业人士。" 在《Expert Shell Scripting》这本书中，作者Ron Peters深入讲解了Linux或Unix环境下的shell编程技术。shell脚本是系统管理员和开发者日常工作中不可或缺的工具，用于自动化任务执行、文件管理以及系统维护等。通过阅读本书，读者可以掌握以下关键知识点： 1. **基础语法**：书中会涵盖shell脚本的基本结构，包括变量定义、条件语句（if-else）、循环结构（for, while）以及函数的使用。 2. **命令行接口**：了解如何在shell脚本中调用各种Linux/Unix命令，如grep、sed、awk等，进行文本处理和文件操作。 3. **输入/输出重定向**：学习如何利用重定向符号（<, >, >>）将命令的输出导向文件，或者从文件读取输入，以及管道（|）的使用。 4. **控制流程**：掌握流程控制结构，如case语句，以及如何处理脚本中的错误（错误处理）。 5. **函数与参数**：学习创建自定义函数，传递参数，并理解位置参数和特殊变量。 6. **脚本调试与测试**：学习如何使用set命令来调试脚本，以及编写测试用例确保脚本的正确性。 7. **正则表达式**：深入理解正则表达式，以及如何在shell脚本中使用它们进行模式匹配和字符串操作。 8. **环境变量与别名**：了解环境变量的作用，如何设置和使用，以及如何定义命令别名以简化常用命令。 9. **脚本权限与执行**：理解chmod命令的使用，确保脚本有正确的执行权限。 10. **脚本优化**：学习如何提高脚本效率，避免性能瓶颈，以及编写可维护和可扩展的脚本。 11. **shell脚本设计模式**：书中可能包含一些常见的shell脚本设计模式，提供解决特定问题的模板。 12. **技术审阅**：本书经过了Brian Culp的技术审查，确保内容的专业性和准确性。此外，书中还可能包含一些实战案例，帮助读者将理论知识应用到实际工作场景中。通过本书的学习，无论是系统管理员还是开发者，都能提升shell脚本编写能力，提高工作效率。

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页未读，继续阅读

thorfei

粉丝: 2
资源: 8

Shell脚本专家指南：进阶编程技巧

Shell编程进阶教程：高级用法与实践

Shell编程进阶：awk与sed用法详解

Linux Shell编程进阶指南与UNIX智慧

Shell编程（2）之Shell编程进阶

Shell编程进阶与实践

Shell编程进阶与实用技巧

Shell编程进阶：正则表达式实战指南

嵌入式Linux开发：Shell编程进阶指南

Shell编程进阶：实战if, for, while, case与数组操作

Shell编程进阶：正则表达式与通配符

最新资源