Automating Linux and Unix System Administration

The author focuses solely on how UNIX and Linux system administrators can use well-known tools to automate tasks, even across multiple systems.

“From the reviews: "While automating a system is the dream of all sysadmins, there is such a thing as too much automation. Thankfully, this book recognises it. It covers just everything a sysadmin needs to know ... . If you're a sysadmin - get this book, you won't be sorry. Highly recommended." (Paul F. Johnson, CVU/ ACCU/ Reviews, February, 2004)”

From the reviews:

"While automating a system is the dream of all sysadmins, there is such a thing as too much automation. Thankfully, this book recognises it. It covers just everything a sysadmin needs to know … . If you’re a sysadmin – get this book, you won’t be sorry. Highly recommended." (Paul F. Johnson, CVU/ ACCU/ Reviews, February, 2004)

Nathan Campi is a UNIX and Linux system administrator by trade, working as a UNIX operations manager in San Francisco. His system administration experience is almost entirely with companies with large-scale web operations based on open source software. In his copious free time, he enjoys jogging, watching spaghetti westerns, experimenting with Linux systems, and spending time with his family.

The system administrator is one of the users of a system, and something more. The administrator wears many hats, as knowledgeable user of UNIX commands, as an operator of system hardware, and as a problem solver. The administrator is also called upon to be an arbitrator in human affairs. A multiuser computer is like a vast imaginary space where many people work and utilize the resources found there. The administrator must be the village elder in this space and settle the disputes that may arise with, hopefully, the wisdom of Solomon. --Rebecca Thomas and Rik Farrow (UNIX Administration Guide for System V, Pearson PTR, 1989) We find it interesting how little UNIX system administration has changed in the last twenty years. If you substitute "computer network" for "multiuser computer," this description still fits perfectly. The main difference in UNIX system administration between 1989 and 2008 (besides ubiquitous networking) is the sheer number of systems that the average system adm- istrator deals with. Automation is the primary tool to deal with the chaos that can result from so many systems. With it, you can deploy systems identically every time, restore s- tems to a known good state, and implement changes reliably across all systems (or only an appropriate subset).

This item is eligible for free returns within 30 days of delivery. See our returns policy for further details.