Time Management for System Administrators

Time Management for System Administrators

Thomas A. Limoncelli

Language: English

Pages: 228

ISBN: 0596007833

Format: PDF / Kindle (mobi) / ePub

Time is a precious commodity, especially if you're a system administrator. No other job pulls people in so many directions at once. Users interrupt you constantly with requests, preventing you from getting anything done. Your managers want you to get long-term projects done but flood you with requests for quick-fixes that prevent you from ever getting to those long-term projects. But the pressure is on you to produce and it only increases with time. What do you do?

The answer is time management. And not just any time management theory--you want Time Management for System Administrators, to be exact. With keen insights into the challenges you face as a sys admin, bestselling author Thomas Limoncelli has put together a collection of tips and techniques that will help you cultivate the time management skills you need to flourish as a system administrator.

Time Management for System Administrators understands that an Sys Admin often has competing goals: the concurrent responsibilities of working on large projects and taking care of a user's needs. That's why it focuses on strategies that help you work through daily tasks, yet still allow you to handle critical situations that inevitably arise.

Among other skills, you'll learn how to:

  • Manage interruptions
  • Eliminate timewasters
  • Keep an effective calendar
  • Develop routines for things that occur regularly
  • Use your brain only for what you're currently working on
  • Prioritize based on customer expectations
  • Document and automate processes for faster execution

What's more, the book doesn't confine itself to just the work environment, either. It also offers tips on how to apply these time management tools to your social life. It's the first step to a more productive, happier you.

PHP, MySQL, JavaScript & HTML5 All-in-One For Dummies

MySQL High Availability: Tools for Building Robust Data Centers

QOS-Enabled Networks: Tools and Foundations (Wiley Series in Communication Networking and Distributed Systems)

Grand Theft Auto V (Signature Series Strategy Guide)

OS X Mavericks: The Missing Manual

Beginning NFC: Near Field Communication with Arduino, Android, and PhoneGap











run to the stationery store to buy filler paper for your PAA. I'll wait (even if you have to run to the store). OK, are you back? Did you record your appointment? There, that wasn't so bad, was it? Always Call If You Are Going to Be Late or Miss an Appointment It is better to call someone when the meeting is supposed to be starting than to leave him wondering where you are. Even if your lateness is embarrassing, in this age of ubiquitous cell phones, there's no excuse for not calling. In an

low ratio of benefit to time spent. Everything has some kind of benefit. Spending five hours playing video games has an entertainment benefit. However, other things have benefits that might be more valuable to you. For example, spending the same Figure 11-1. amount of time to increase your quality of living by doing home repairs has longer-lasting benefits than blasting millions of pixilated aliens. The things that waste our time at work are different—phone calls with people who never

done: aliases.db is newer than aliases. make is lazy and will calculate the minimum amount of work required to do what you ask. It makes these decisions based on the timestamps of the files. Here's another Makefile code sample: file1.output: file1.input command1 file.output file2.output: file2.input command2 file2.input >$@ In the first example, the command to be run uses stdin and stdout (file redirection using < and >) to read file.input and write file.output. The second example

Here's a complete example. There are two files that need indexing if they change: aliases and access. If either of them has been reindexed, postfix is told to reload. They also are both pushed to server2 if they change. Finally, the command cd /etc && make is sent to server2 if and only if one or more of the files has been pushed to it. By carefully constructing the recipes with proper dependencies, and touching *.done files where required, make will do the absolute minimal amount of work to

by pressing Ctrl-C. We want enough lines to do something useful, and then we'll process it all. So, let's take the first 100 lines of data: $ sudo tcpdump -l -n arp | grep 'arp who-has' | head -100 Again, we run this and see that it comes out OK. Of course, I'm impatient and changed the 100 down to 10 when I was testing this. However, that gave me the confidence that it worked and that I could use 100 in the final command. You'll notice that there are a bunch of headers that are output, too.

Download sample