Slashdot Mirror
Automating Unix and Linux Administration
From the outset, Bauer takes a straightforward and principled approach to problem analysis. Usually starting with anecdotal example scenarios (many of which will have you saying "been there before") and progressing through ideals, goals and consequences, he examines many of the common issues facing system administrators with candor and realism. Almost nowhere in the book does the author assume an authoritarian stance; he questions his own decision making process and encourages the reader to come up with exceptions to his rules. Fundamentally Bauer has one goal -- to develop a comprehensive system for reliably automating the tedious but important tasks that all system administrators face on a recurring basis.
Admittedly, it would be a fallacy for any book to claim complete and comprehensive coverage of all things related to system administration and Bauer does no such thing. When the author touches on topics that obviously require more depth than a single chapter can afford, he is certain to include at least one reference (and in many instances more) to alternate publications without bias to any particular publisher or author. Having said that, the book's scope and depth of topic coverage is impressive. Starting with an exhaustive examination of SSH and progressing through cfengine, NFS, LDAP, RPM and Tripwire (just to name a few) Bauer provides carefully detailed instruction on how to automate tasks ranging from simple network management and software packaging to security, monitoring and backups. The author even goes so far as to suggest methods for efficiently front-ending automation systems for the less technical of users.
Although not expressly stated in the text, the overall theme of the book is walk on the shoulders of giants. Starting with simple example scripts (in both Bash and Perl) and many single-line commands, Bauer builds on the content of each previous chapter as the book progresses. Examples shown in early chapters are incorporated into more complex systems one step at a time. Following along is easy, each script or command is detailed on a line-by-line basis, and because of Bauer's principle-based approach the reader is rarely left wondering why the author has chosen a particular tool or implementation. More often than not the elegance of how Bauer pieces together methods and procedures will excite you about the possibilities for automation of your own systems.
Although Bauer explicitly states that readers are presumed to have more than a modicum of experience in system administration, even the novice administrator, as well as those that are responsible for only a handful of machines, will find this book invaluable. Also included are three appendices which provide an easy introduction to basic shell tools, creating your own RedHat distribution and how to package software as RPMs. These portions of the book alone justify the less than $40 price tag, but for those who run clusters or data centers, this book stands to save you countless hours of repetitive headaches. Published by apress and boasting nearly 600 pages, this lively read has made itself a permanent addition to at least one reference library.
You can purchase Automating Unix and Linux Administration from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
here
I have over 70 freaks, do you?
Ref: Amazon has this book for $5 less than bn and with free shipping
(yes, this link does generate commissions at no extra cost to you.)
Automating UNIX and Linux Administration will focus on automating the tedious daily tasks of system administration. It will provide real-world examples and explore the existing tools that will help with this task. Although the book will provide brief overviews of tools and technologies that are covered, the author will assume the reader knows how to edit a configuration file or mount a file system. The book will focus on putting these tools to use in the real world, such as how to use a set of Perl scripts to manage your user accounts across 1000 machines. It will not show you how to write a basic 'Hello World' program in Perl nor contain a Perl function reference or summary.
The techniques, methods and tools covered in this book will help on a single system, but will be much more useful across multiple systems. Whether you are managing 2 or 5,000 systems, whether they are desktops, servers, or a Beowulf cluster, you will benefit from this type of automation. Although some of the book will be Linux-specific, most of it will apply to any UNIX system. The book will also focus on automating tasks across multiple variants of UNIX.
(Kudos to Amazon.com)
I have over 70 freaks, do you?
55? more link 5500
Have book reviews on slashdot become about who can get the earliest links to their amazon.com partner site?
This books looks interesting (to me) and I might actually take a trip to the book store to check it out. But the comments (so far) aren't about the book.
No more Micro$oft bashing from me. Its like bashing at the special olympics.
You can automate yourselves out of a job!
;)
Unless of course you pick up 'Making Management Think You're Actually Working for Dummies'.
Remember, kids, always, always appear to be busy, lest management will either find you unnecessary or volunteer you for even more work.
Perl for System Administration.
Trolls lurk everywhere. Mod them down.
That just sounds so bad. I prefer the term "minimal keystroke solution". -B
2b2b2b415448300d
Don't you mean: "Obligatory Amazon Referral Link to give me commission."
Bastard...
1. Decide that automating takes too much time
2. Do everything by hand
3. Fuck up once too often
4. Decide that automating is necessary
Don't know about the rest of you.
- If this book obviously doesn't have any downsides (at least you didn't mention any) - why did it get only eight points? (assuming maximum would be 10, as usual. Or do you mean eight out of eight points?;)
- 547 pages - I'd say that's nearer 500 pages than 600 pages. Or simply around 550 pages. But certainly not nearly 600 pages.
At all - thanks for the review!Well, there's also jewelry
Call me a cynic, but I am under the impression that without knowledged personnel (i.e. who don't need autowhatever) there will be, almost as sure as a natural law, a corrupt server or an autocrash. Don't do away yourself with knowledge - see what happened in the Windows world.
I own the book and have been using it for a couple of weeks now. All in all, I think it's a great resource if you already have a fair amount of linux knowledge. I purchased it primarily because of its coverage of cfengine but found it useful for other purposes as well.
Definitely not for the newbie system administrator (nor does it pretend to be). But it is a great resource if you're looking to administer more boxes with less bodies.
Gentoo Linux http://gentoo.org/
Simple question, that isn't really answered in the review. How much of this book is generic Unix/Unixlike information, how much is specific to a single vendor OS, and how much is specific to Linux?
/sbin/sh, for admin scripting)
I'd like to think that most of this stuff is fairly transportable, but when I hear about "bash scripts," I wonder if it's the reviewer or the book that's pushing Linux-centricisms. (and yes, I know that bash is available everywhere, blah blah blah. It still doesn't make it a valid replacement for
"People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
This is nothing new. Unix admins have been automating machines since before Linux was even a glimmer in Trovald's eye. The only difference I think, is that there are a great deal more admins today who don't know their craft very well. To many fuzzy GUI widgets (that invariably screw things up) getting in the way.(You hear me RedHat?!)
Javascript + Nintendo DSi = DSiCade
I know it doesn't apply in all cases, but if you're just running a web server my experience is that running it all out of Knoppix RAMDisk just makes sense in every way. It's faster, it's cheaper and if it screws up, just start from scratch. But since it's so cheap why not run redundant servers? It's a winner from every angle.
Yeah, you need to make a few little scripts to automate your rebuilding process, but once you've done that it's about as maintenance free as you can possibly imagine.
Of course a web server is a limited example and I assume the book covers more than just such a simple case, but for a lot of net server tasks it's the way to go and yet I get the impression a lot of people don't quite get it yet.
Where can I sign up to be a member of this "wet-insertion" team that gets to whack people???
Goddamit, I'm just trying to make a buck here, since I automated our system administration and put myself outta a job!!!
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
If RPM weren't such a mess, it might be more convenient to make RPMs of the packages you build from source but want to install the same exact binary on all the other machines. I just make Slackware style tarballs, so it's real easy; no spec file needed.
now we need to go OSS in diesel cars
i get most of my stuff from reading periodicals while sipping chai at Borders. and websites like the Linux Documentation Project.
http://www.tldp.org
-- I hereby announce, on behalf of my great ancester Oog, a retroactive patent on THE WHEEL.
RE: >
:)
and necessity is the mother of invention, does this mean laziness and necessity get together and have nasty sex before inventing something
sorry to be this guy but otherwise...
i'd think this book is about working for dummies....instead of "Making Management Think You're Actually Working, for Dummies"
unless you really do mean "working for Dummies", in which case, if you make management think that...you might not be working for the dummies anymore.
We're like rats, in some experiment! -- George Costanza
man cron
are you donald rumsfeld?
why waste money on a book?
This message brought to you by your local chapter of the NEA.
I have just about any task down to issuing one command:
"Brian, go overto server X and do such-and-such"
here
I wish you would stop posting amazon links to make referral money. It's not like you're actually contributing anything to the discussion of the book. you're just abusing the fact you got to post early on a book review.
Fuck Beta. Fuck Dice
That's pretty funny. Actually, too funny.
Humour beyond Beowulf cluser "jokes" is wasted on this site.
I think you meant "more like 5500"
One of the problems we have, is when you have clusters with 100+ machines, and need to push configs, or gather stats off each box.
On solaris, we run a script called "shout" that does a for/next loop that ssh's into each box and runs a command for us. We also have one called "Scream" which does some root privilege ssh enabled commands.
Nortel has a nice program called CLIManager (use to be called CLImax), that allows you telnet into multiple passports and run commands. Same idea, but the program formats data to display. Say you wanted to display "ipconfig" on 50 machines, this would format it, so you have columns of data, easy to read and put in reports.
Also, has a "Watch" command that will repeat a command, and format the data. Say you want to display counters.
I have not seen an opensource program that does the same as "CliManager" but its has to be one of the best idea's that should be implemented in opensource. Basically, it logs into multiple machines, parses and displays data, and outputs all errors on another window to keep your main screen clean.
Think of logging into 10 machines, and doing a tail -f on an active log file. Then the program would parse the data, display it in a table, and all updates would be highlighted.
I havnt spoken to the author of CliManager, but I guess he also hated logging into multiple machines, and running the same command. This program has been updated over the years, and is now the standard interface to the nodes. It just uses telnet and a command line, but you can log into 100's of nodes at once.
Wish I could post pics and the tgz file, maybe someone from Nortel can comment. (Runs on Solaris, NT and linux)
Would be for Slashdot to publish Amazon affiliate links together with Barnes and Noble. I usually buy from Amazon because of cheaper price and I their Trivia program always leaves about $2-3 in my account, taking the price even lower.
However, I have never clicked on Amazon troll link before on this site, just went to the URL directly and searched by ISBN.
Sir Haxalot? More like Sir Spamsalot
Certainly I haven't read the book but it looks as if Kirk is offering examples of how to write scripts to handle everyday gruntwork. Good idea.
:) and it's amazing the amount of
admins that don't have the slightest idea how to write the simplest
loop. Or use ksh, bash, or csh's cmd history. Or vi.
But I say to those that call themselves sys.admins, Learn how to script!!!
I work at a large bankrupt telcom
Maybe this is just a corporate thing. They were raised, in a sense, in a setting where all they had to do was add users and replace disks. Maybe they never learned how to do anything else.
Back in '83 I took manuals home and poured over every page, every weekend for months. That didn't make me a good admin but it gave me a good foundation. From there I had to just halfway use my head (imagination?) and start writing scripts. Ugly? Sure. Did they get better? Of course!
Now I play admin on 110+ machines, and I stay bored. Why? Because I've written a response engine in Expect that handles most of my everyday problems. I call it AGE, Automated Gruntwork Eliminator.
There's no way I could have done this if I had just sat back and floated, not put in a bit of effort to learn new things.
T.
...the reviewers should be obligated to explain why the book wasn't a 10/10. In many cases they do say why, but in this case I thought that 8/10 was very stingy considering the types of good compliments that he gave. He could have kept the same compliments & the score, if he just explained why he took off 2 points.
testing out my trending skills
But the comments (so far) aren't about the book.
This is slashdot. Nobody reads the articles before posting. Do you really expect them to read a whole BOOK before posting?
;)
If you're thinking of this computer or that computer then you won't make an effective systems administrator. You have to see the network of all of the computers as a single whole and treat them as such.
Once you've got the mindset change sorted, 10, 100, 1000 systems it makes no difference, it's just as simple to manage. You aren't managing individual computers, you're managing an infrastructure.
Course, you actually have to be competent as well... Obviously.
Government of the people, by corporate executives, for corporate profits.
It is definately on my list of Expensive Books (50. Am I cheap?)to Buy.
=============
Together, we will drive the rats from the tundra.
Likewise, when they switched to grub, I was whizzed. I spent all this time learning lilo, just to have grub dropped on me, which I have gotten used to and now prefer :)
I have no intention of "getting used to" disk druid though, as long as fdisk is still around, I'll use that.
If something I said can be interpreted two ways, and one of the ways makes you sad or angry, I meant the other one.
because all sir haxalot does is post early with links to places that are EASILY found by almost anyone if they care to, but a moderator will compulsively mod up informative because he doesn't want to waste his mod points.
Then he can post an Amazon link and get it clicked on like all the links in all his other posts. The effect is further amplified as it's highly visible, near the top as he's posting at +2 because of said karma-whoring.
Basically, it's because it's Sir Haxalot doing it, and he's taking advantage of Slashdot's structure to make money for himself. I say ignore it on principal, Amazon be damned. Slashdot could just as easily put it's own referral link in the article itself, but they don't because it would be a conflict of interest. That doesn't mean everyone else should attempt to ride it's coattails.
Fuck Beta. Fuck Dice
Plus my products are the results of my effort, not some referral marketing scheme.
This might very well be a book I'll pick up sometime. I'm always looking for more ideas.
I maintain about ~170 remote Linux boxes (in our company's retail stores and warehouses), as well as our ~30 or so inhouse servers.
I went through a lot of work to enable our rollout and conversion to go more smoothly. The network and methodology for users, printers, etc. is extremely simplified and patterened.
For each of the 3 'models' of PCs we use, I have a master system that I produced. I used Mondo Rescue to produce CD backups of these systems. These systems act as serial terminal controllers, print spoolers, routers, desktop system usage (OpenOffice, Mozilla, Kmail under KDE), and other functions as needed.
When we need to replace a system, or rollout a new location, we grab a system, pop in the Mondo CD, and do a nuke restore. When done, we have a standard configuration user that we log in as. It runs a quick implementation script where you answer anywhere from 3-8 questions (depending on the system type and options), and it configures everything. All networking, users, sets up Kmail, configures all printers and terminals (we use Comtrol Rocketport serial boards), and so on.
If the system is physically ready, we can have it ready software-wise in about 20 minutes (2 CDs to restore).
Updates are done via a couple different methods. I use SSH (over our internal VPN, using key authentication) in scripts to do most updates. If I need to do anything major, such as recently updating Mozilla, we do a CD distribution. The users have a simple menu to take care of running the update for them, even with autorun under KDE. Just pop in the CD, and it automatically takes them into the menu they need.
All logs are duplicated across the network to a central server, but intrusion is less likely as these systems sit on a private frame network. They do, however, have fully secured network setups, as we use cheap dial-up internet access as a backup in case the frame circuit goes down.
I can't help but feel every day like this is just one big hack/kludge, but it works, works damned well, and was about half the cost of any other solution (i.e. higher end Cisco routers to handle various functions, and using Equinox ELS-IIs or the like...those pieces of crap never would work right, we finally pulled only 2 we had in use, and they are currently collecting dust in a storage cabinet).
Needless to say, I am *always* looking for ideas to improve upon this.
Full details, including sample chapter, here.
/.gods have already got to this thread: "Duh, it's easy, just use cron/telnet/syslog!" Do any of you people have more than a home PC to maintain? Come to that, would anyone trust you with more than that?
I see the
Ade_
/
Big Bubbles (no troubles) - what sucks, who sucks and you suck
On a similar topic, I am a longtime Unix/Linux admin who has inherited a large farm of Windows servers (don't ask, I'm not happy about it either). This is probably about the worst place to ask this, but I'll give it a shot:
Do any of you have recommendations for books/URLs on how to effectively manage a large Windows cluster using automated methods?
Thanks in advance for any useful information.
--= ThreeTee =--
Just a quick little note. I've read it, and it's good.
:) and It was easy to read, adn very informative.
I'm a pretty smart guy ("hah, yea right"-My Co-Worker)
I'd put this on my top 10 list, maybe even top 5.
Good work dude.
Welcome to the End
And stop posting as an AC to defend yourself.
You are trying to trick people into clicking your links. He tries to do some decent work.
You are a fucking idiot, and I will use as many mod points as I can to mod you down, Sir Idiotalot.