Python在Unix和Linux系统管理中的应用

需积分: 9 10 浏览量更新于2024-07-23 收藏 3.42MB PDF 举报

"Python for Unix and Linux System Administration" 是一本由O'Reilly出版的书籍，旨在帮助读者掌握如何使用Python语言进行Unix和Linux系统的管理。这本书可能是由经验丰富的系统管理员和Python程序员共同编写的，旨在结合两种强大的工具——Python编程语言和Unix/Linux操作系统，提升系统维护和自动化的能力。在Unix和Linux环境中，Python被广泛用于系统管理和自动化任务，因为它提供了丰富的库支持和易于理解的语法。本书可能会涵盖以下关键知识点： 1. **Python基础**：包括变量、数据类型、控制流语句（如if-else、for循环、while循环）、函数定义和调用、类和对象等。 2. **文件和目录操作**：Python中的文件I/O（读写操作），文件和目录的创建、删除、移动等，以及处理路径和权限的方法。 3. **进程和线程管理**：如何使用Python启动、控制和管理Unix/Linux进程，包括子进程的创建、信号处理、线程同步等。 4. **网络编程**：使用Python进行网络通信，包括套接字编程、HTTP请求、FTP客户端实现等。 5. **系统接口和调用**：通过Python的os、sys、subprocess等模块与Unix/Linux系统接口交互，执行shell命令，解析命令输出等。 6. **系统监控和日志处理**：使用Python收集系统性能数据，监控资源使用情况，以及处理和分析日志文件。 7. **自动化脚本编写**：如何构建复杂的自动化脚本，执行定期任务，例如备份、系统维护、配置管理等。 8. **错误处理和调试**：学习如何在Python中处理异常，进行有效的错误报告和调试。 9. **安全实践**：了解如何在Python脚本中实施安全措施，如输入验证、权限控制、加密等。 10. **相关工具和库**：介绍Python在Unix/Linux系统管理中常用的第三方库，如Pexpect（进程控制）、paramiko（SSH库）和fabric（自动化部署）等。除了书籍本身，O'Reilly出版社还提供了多种相关的资源，如其他书籍（如"Essential System Administration", "Learning Python", "Linux Networking Cookbook"等）、网络资源、会议和在线参考图书馆Safari Bookshelf。这些资源可以帮助读者进一步扩展和深化对Python在Unix和Linux系统管理中的应用。访问oreilly.com和oreillynet.com，可以获取更多关于开源和新兴技术的新闻、事件、文章、博客、样章和代码示例。此外，O'Reilly的会议为创新者提供了交流平台，将最新的工具和技术转化为实际技能。Safari Bookshelf在线参考图书馆则为程序员和IT专业人员提供了超过1000本书的搜索和订阅服务，是持续学习和提升技能的重要资源。

Acknowledgments

Noah’s Acknowledgments

As I sit writing an acknowledgment for this book, I have to first mention Dr. Joseph E.

Bogen, because he made the single largest impact on me, at a time that it mattered the

most. I met Dr. Bogen while I was working at Caltech, and he opened my eyes to another

world giving me advice on life, psychology, neuroscience, math, the scientific study of

consciousness, and much more. He was the smartest person I ever met, and was some-

one I loved. I am going to write a book about this experience someday, and I am sad-

dened that he won’t be there to read it, his death was a big loss.

I want to thank my wife, Leah, who has been one of the best things to happen to me,

ever. Without your love and support, I never could have written this book. You have

the patience of a saint. I am looking forward to going where this journey takes us, and

I love you. I also want to thank my son, Liam, who is one and a half, for being patient

with me while I wrote this book. I had to cut many of our guitar, piano, and pushup

lessons short, so I owe you payback times two, little goat.

To my mom, I love you, and thank you for encouraging me throughout life.

Of course, I want to thank Jeremy M. Jones, my coauthor, for agreeing to write this

book with me. I think we were a great team with different, but complementary styles,

and we wrote a great book. You have taught me a lot about Python, and have been a

good partner and friend. Thanks!

Titus Brown, whom I suppose I have to call Dr. Brown now, was the person that got

me interested in Python to begin with, when I met him at Caltech. He is another ex-

ample of how one person can make a difference, and I am glad to consider him an “old”

friend, the kind money can’t buy. He kept asking me, “Why don’t you use Python?”

And then one day I did. If it wasn’t for Titus, I would certainly have continued down

the Java and Perl path. You can read his blog here: http://ivory.idyll.org/blog.

Shannon Behrens has a heart of solid gold, a mind as sharp as a razor, and a knowledge

of Python that is truly scary. I first met Shannon through Titus, ironic again, but he and

I became quick friends. Shannon is the real deal in every sense of the word, and has

taught me a tremendous amount about Python, in fact, staggering would be a better

word. His help with Python, and editing this book has been incredible, and I owe him

tremendously. I shudder to think of what it would have looked like without him. I can’t

ever imagine a company being foolish enough to let him get away, and I look forward

to helping him with his first book. Finally, he is just an incredible technical reviewer.

You can read his blog here: http://jjinux.blogspot.com/.

Doug Hellmann was our other star technical reviewer and was exceptionally productive

and helpful. Jeremy and I are extremely fortunate to get someone of his caliber to review

the book. He went above and beyond his call of duty, and is truly a force of efficiency

Preface | xv

to reckon with. He was also a great source of motivation while we worked together at

Racemi. You can read his blog here: http://blog.doughellmann.com/.

Thanks to Scott Leerseen for reviewing our book and giving us good advice along the

way. I also especially enjoyed our code review battles. Just remember, I am always right.

Thanks to Alfredo Deza for the work on making an Ubuntu virtual machine for the

book, your expertise was greatly appreciated.

A very large thanks to Liza Daly, for providing good feedback on some really early, and

rough, parts of our book. This was tremendously helpful.

Special thanks to Jeff Rush for his advice and reference material on Buildout, Eggs, and

Virtualenv.

Thanks to Aaron Hillegass who has given me some great advice and help along the way,

and who has a great training company, Big Nerd Ranch. He is a special person, who I

am lucky to have met. Thanks to Mark Lutz, who I had the pleasure of taking a Python

training course from, and who has written some great books on Python.

Thanks to the people in the Python community in Atlanta, and the members of PyAtl:

http://pyatl.org; you have all taught me a great deal. Rick Copeland, Rick Thomas,

Brandon Rhodes, Derek Richardson, Jonathan La Cour, a.k.a Mr. Metaclass, Drew

Smathers, Cary Hull, Bernard Matthews, Michael Langford, and many more I have

forgotten to mention. Brandon and Rick Copeland in particular have been very helpful

and are awesome Python programmers. You can read Brandon’s blog at http://rhodes

mill.org/brandon/.

Thanks to Grig Gheorghiu for giving us expert sysadmin and testing advice and for

giving us a kick in the butt when we needed one.

Thanks to my former employer Racemi, and the CTO/Founder, Charles Watt. I learned

a lot from you and was glad you knew which competitive buttons to push. Just re-

member I will kick your butt at writing code, a 26-mile run, or a 200-mile bike ride any

day, just tell me where and when.

Thanks to Dr. Nanda Ganesan, who was a great mentor in graduate school at CSULA.

You taught me a lot about information technology and life and encouraged me to think

big.

Thanks to Dr. Cindy Heiss, who was my professor for my undergraduate degree in

nutritional science. You got me started on web development, encouraged me to believe

in myself, and ultimately made an impact on my life, thanks!

Thanks to Sheldon Blockburger, who let me try out for Division I decathlon as a walk-

on at Cal Poly SLO. Even though I didn’t make the team, you showed me how to be a

fierce competitor and warrior, and taught me the self-discipline to run 200-meter in-

tervals by myself. I believe weekly 200-meter interval workouts make me a better soft-

ware engineer.

xvi | Preface

There were many other people who helped tremendously along the way, including

Jennifer Davis, yet another friend from Caltech, who gave us some great feedback; some

of my friends and coworkers at Turner; Doug Wake, Wayne Blanchard, Sam Allgood,

Don Voravong; some of my friends and coworkers from Disney Feature animation,

including Sean Someroff, Greg Neagle, and Bobby Lea. Greg Neagle in particular taught

me a lot about OS X. Also, thanks to J.F. Panisset, who I met at Sony Imageworks, for

teaching me quite a bit about engineering in general. Although he is now a CTO, he is

another rare catch for any company.

I would like to thank a few others who made some important contributions: Mike

Wagner, Chris McDowell, and Shaun Smoot.

Thanks to Bruce J. Bell, who I worked with at Caltech. He taught me quite a bit about

Unix and programming over the years, and I owe him greatly for it. You can read his

material here: http://www.ugcs.caltech.edu/~bruce/.

Also thanks to Alberto Valez, my boss at Sony Imageworks, for being possibly the best

boss I ever had and giving me the chance to completely automate my job. Thanks to

film editor Ed Fuller, who helped with advice on the book, and was a good friend during

this process.

Thanks to many people in the Python community. First, thanks to Guido van Rossum

for writing a great language, for being a great leader, and for being patient with me

when I asked for advice on the book. There are so many rock stars in the Python com-

munity who crank out useful tools that I use everyday. They include Ian Bicking, Fer-

nando Perez and Villi Vainio, Mike Bayer, Gustavo Niemeyer, etc. Thanks! Thanks to

the great book by David Beazely, and his fantastic tutorial at PyCon 2008 on Genera-

tors. Thanks to other writers about Python and systems administration as well. You

can find links to their work here: http://wiki.python.org/moin/systems_administration.

Thanks also to the Repoze crew: Tres Seaver and Chris McDonough (http://repoze.org/

index.html).

Special thanks to the great tools, advice, and tolerance from Phillip J. Eby on the

setuptools section. Also, thanks to Jim Fulton who tolerated my questions about ZODB

and buildout, with a crazy schedule. Additional thanks to Martijn Fassen, who taught

me about ZODB and Grok. If you want to see the future of Python web development,

check out Grok: http://grok.zope.org/.

Thanks to Red Hat Magazine staff, Julie Bryce, Jessica Gerber, Bascha Harris, and Ruth

Suehle, for letting me try out ideas we used in this book in the form of articles. Also,

thanks to Mike McCrary at IBM Developerworks, for letting me write articles to try out

ideas we used in this book.

I want to thank the multitudes of people who told me at one point in my life that I

couldn’t do something. At almost every step, I have met discouraging people who told

me everything from I would never get into the college I wanted to to I would never learn

to program. Thank you for giving me the extra motivation to succeed at my dreams.

Preface | xvii

Humans can create their own reality if they truly believe in themselves, and I would

encourage everyone to give themselves a chance to do what they truly want to do.

Finally, thanks to O’Reilly and Tatiana Apandi, for believing in my original pitch for a

book on Python and Systems Administration. You took a chance and believed in me

and Jeremy, and I thank you for that. Although Tatiana left O’Reilly near the end of

our book to pursue her dreams, her impact was still felt. I also want to thank our new

editor Julie Steele, who has been supportive and helpful every step of the way. You have

really provided a sea of calm that I personally appreciated greatly. I look forward to

hearing great things in the future from Julie, and I’m excited to work with her again.

Jeremy’s Acknowledgments

After reading Noah’s list of thanks, it makes me feel both ungrateful, because I know

my list won’t be that long, and at a loss, because I think he covered nearly everyone

that I wanted to thank.

First, I must thank my God, through Whom I can do all things and without Whom, I

can do nothing.

First in an earthly sense, I thank my wife, Debra. You kept the children engaged with

other activities while I worked on the book. You enforced the so-often reapeated rule

“Don’t bother Daddy while he’s working on his book.” You encouraged me when I

needed it, and you also gave me a lot of space, which is what I needed most. Thank

you. I love you. I could not have written this book without you.

I also must thank my sweet children, Zane and Justus, for their patience through the

process of my writing this book. I missed out on a lot of trips to Stone Mountain with

you both. I still put one of you to bed most nights, but I missed out on staying in there

long enough to fall asleep with you, like I used to. I missed out on the last several weeks

of Kid’s Rock on Wednesday nights. I missed out on so much, but you bore it patiently.

So, thank you for your patience. And thank you for your excitement as you hear that

I’m almost done with the book. I love you both.

I want to thank my parents, Charles and Lynda Jones, for their support through the

course of my writing this book. But more than that, I want to thank them for being a

living example of a strong work ethic, of earning everything you have, of working hard

to better yourself, and of spending money wisely. Those are lessons I hope to pass on

to Zane and Justus.

Thank you to Noah Gift, my coauthor, for getting me into this mess. It has been hard,

harder than I thought and definitely one of the hardest things I’ve ever done in my life.

I think it says a lot about a person when you work on something like this with him and

at the end, you can still think of him as your friend. Thanks, Noah. This book would

not have begun if not for you.

xviii | Preface

I want to thank our team of reviewers. I think that Noah has already thanked all of you,

but I want to thank everyone that I can: Doug Hellman, Jennifer Davis, Shannon JJ

Behrens, Chris McDowell, Titus Brown, and Scott Leerseen. You guys were awesome.

There were times when I thought that I had something spot-on and you readjusted my

thinking. Or you just brought a completely different perspective to the book and helped

me see my work through a different set of eyes. (That was mostly you, Jennifer. If the

text processing chapter is useful for sysadmins, it’s mostly because of you.) Thank you

all.

I also want to thank our editors, Tatiana Apandi and Julie Steele. You guys handled

the hard stuff, freeing us up to work on the book. You both eased our burden along

the way. Thank you.

I’d also like to thank Fernando Perez and Ville Vainio for your amazing feedback. I

hope I’ve done IPython justice. And thank you for IPython. I feel like I couldn’t live

without it.

Thank you Duncan McGreggor, for helping me get the Twisted code in better shape.

Your comments were extemely helpful. And thank you for working on Twisted. It is

an amazing framework. I hope to use it more, real soon now.

I thank Bram Moolenaar and everyone who has ever worked on the Vim editor. Almost

every word and XML tag that I wrote flowed through capabilities Vim. I picked up a

few tricks along the way that I’ll incorporate into my daily editing habits. Vim made

me more productive. Thank you.

I also want to thank Linus Torvalds, the Debian folks, the Ubuntu folks, and anyone

else who has ever worked on Linux. Almost every word that I typed was done on Linux.

You made it incredibly simple to set up new environments and test different things.

Thank you.

Finally, but by no means least, I want to thank Guido van Rossum and everyone who

has ever done any work on Python. I have been benefitting from your work for a number

of years now. I was hired for my last two jobs because of Python. Python, the language,

and Python, the community, have been both a great joy for me since I started working

with it sometime around 2001–2002. Thank you. Python has been very good to me.

Preface | xix

剩余457页未读，继续阅读

Book_Chan

粉丝: 0
资源: 1

Python在Unix和Linux系统管理中的应用

Python for Unix and Linux System Administration

Python for Unix and Linux System Administration 无水印pdf

Python for Unix and Linux System Administration/Python UNIX和Linux系统管理指南(源代码)

C:\Windows\system32>where python C:\Program Files\Python311\python.exe C:\Users\zhang\AppData\Local\Microsoft\WindowsApps\python.exe

linux 查找python.sh 文件

python.h怎么获取

No Python at 'E:\Python\python.exe 什么意思

System.Diagnostics.Process.Start(@"G:\Software_installation\ArcGIS10.2\ArcGIS10.2\python.exe", @"E:\python_chengxu\村庄追述\耕地.py");

python.exe -m pip install --upgrade pip -bash: python.exe: command not found

最新资源