Linux Server Hacks: 100 Industrial-Strength Tips and Tools

Linux Server Hacks: 100 Industrial-Strength Tips and Tools

Rob Flickenger

Language: English

Pages: 242

ISBN: 0596004613

Format: PDF / Kindle (mobi) / ePub

A competent system administrator knows that a Linux server is a high performance system for routing large amounts of information through a network connection. Setting up and maintaining a Linux server requires understanding not only the hardware, but the ins and outs of the Linux operating system along with its supporting cast of utilities as well as layers of applications software. There's basic documentation online but there's a lot beyond the basics you have to know, and this only comes from people with hands-on, real-world experience. This kind of "know how" is what we sought to capture in Linux Server Hacks.Linux Server Hacks is a collection of 100 industrial-strength hacks, providing tips and tools that solve practical problems for Linux system administrators. Every hack can be read in just a few minutes but will save hours of searching for the right answer. Some of the hacks are subtle, many of them are non-obvious, and all of them demonstrate the power and flexibility of a Linux system. You'll find hacks devoted to tuning the Linux kernel to make your system run more efficiently, as well as using CVS or RCS to track the revision to system files. You'll learn alternative ways to do backups, how to use system monitoring tools to track system performance and a variety of secure networking solutions. Linux Server Hacks also helps you manage large-scale Web installations running Apache, MySQL, and other open source tools that are typically part of a Linux system.O'Reilly's new Hacks Series proudly reclaims the term "hacking" for the good guys. Hackers use their ingenuity to solve interesting problems. Rob Flickenger is an experienced system administrator, having managed the systems for O'Reilly Network for several years. (He's also into community wireless networking and he's written a book on that subject for O'Reilly.) Rob has also collected the best ideas and tools from a number of other highly skilled contributors.Written for users who already understand the basics, Linux Server Hacks is built upon the expertise of people who really know what they're doing.

To the Cloud: Big Data in a Turbulent World

Sets, Logic and Maths for Computing (2nd Edition) (Undergraduate Topics in Computer Science)

Fundamentals of Office 2016

MySQL (4th Edition)

Wireframing Essentials












whitespace), and -n2 tells it to take two arguments at a time on each pass, and feed them to our command (mv). Save the script as ~/bin/albumize. Before you run it, set the $ALBUM environment variable to the name that you’d like injected into the filename just after the first -. Here’s a trial run: rob@catlin:~/Music/Hallucinogen - The Lone Deranger$ export ALBUM="The Lone Deranger" rob@catlin:~/Music/Hallucinogen - The Lone Deranger$ albumize rob@catlin:~/Music/Hallucinogen - The Lone

it in the filesystem: # mkfifo -m 0664 /var/log/debug Then amend the debug line in syslog.conf to include a | like this: *.=debug |/var/log/debug Now debug information is constantly logged to the fifo, and can be viewed with a command like less -f /var/log/debug. This is also handy to set up if you want a process to constantly watch all system messages and perhaps notify you via email when a critical system message is seen. Try making a fifo called /var/log/monitor, and add a rule like this

“hackers” too — and some claim that the hacker nature is really independent of the particular medium the hacker works in. But in the rest of this document, we will focus on the skills and attitudes of software hackers, and the traditions of the shared culture that originated the term “hacker.” There is another group of people who loudly call themselves hackers, but aren’t. These are people (mainly adolescent males) who get a kick out of breaking into computers and breaking the phone system. Real

used that password in a way that might be questionable (on a web site, on a personal machine that isn’t quite up to date, or possibly with an ssh client on a machine that you don’t directly control). If any of these possibilities sound familiar, then consider that an ssh key in the same setting would make it virtually impossible for an attacker to later gain unauthorized access (providing, of course, that you keep your private key safe). See Also: SSH: The Definitive Guide (O’Reilly)

52. Using vtun over ssh to Circumvent NAT52.1. See also: 53. Automatic vtund.conf Generator53.1. Listing: vtundconf 5. Monitoring5.1. Hacks #54-65 54. Steering syslog54.1. Mark Who? 54.2. Remote Logging 55. Watching Jobs with watch55.1. See also: 56. What’s Holding That Port Open? 57. Checking On Open Files and Sockets with lsof57.1. See also: 58. Monitor System Resources with top58.1. See also: 59. Constant Load Average Display in the Titlebar59.1. Listing: tl

Download sample