Time Management for System Administrators
by Thomas A. Limoncelli

The following errata were *corrected* in the 03/07 reprint:


This page was updated February 15, 2007 


Here's a key to the markup:
	[page-number]: serious technical mistake
	{page-number}: minor technical mistake
	<page-number>: important language/formatting problem
	(page-number): language change or minor formatting problem
	?page-number?: reader question or request for clarification
	+n:  n'th paragraph from the top of the page
	-n:  n'th paragraph from the bottom of the page


########################################

(xiii) +1

Computers have their own needs that pull is in many directions.
->
Computers have their own needs that pull us in many directions.

########################################

(xxiii) Acknowledgements

Ralph Loura, Tina Mancuso
->
Ralph Loura, David Malone, Tina Mancuso

########################################

{20} +1

20 attractions per hour
->
12 attractions per hour

########################################

{20} +1

dizzying three hours
->
dizzying five hoursi

########################################

(25) -3

the customer is much more satisfied because she receives visual
proof that I'm attending to his request.
->
the customer is much more satisfied because he receives visual
proof that I'm attending to his request.

########################################

(45) -2

Others schedule one training class per year whether they know what it'll
be.
->
Others schedule one training class per year whether they know what it'll
be or not.

########################################

(86)  4th bullet point

I even record them when I so that I don't accidentally repeat my rejection.)
->
I even record them when I decline so that I don't accidentally repeat my rejection.)

########################################

(86)  last bullet point

System Administrator Appreciation Day (July 28).
->
System Administrator Appreciation Day (last Friday of July).

########################################

(137) +2

how long the conversaion can be.
->
how long the conversation can be.

########################################

(154) +3

there would be no joy in writing, "Francine loves Harvey"
->
there would be no joy in writing "Francine loves Harvey"

########################################

[158] -3

The problems SAs typically deal with fall into four general categories
->
According to R. A. Lichtensteiger, the problems SAs typically deal with fall into four general categories

########################################

(165) code example in bold, line 3

rsync ex:/home/project/alpha ~/project/alpha
->
rsync es:/home/project/alpha ~/project/alpha

########################################

{167} sidebar

added a second paragraph:

Note: When the web pages move from one server to another, SSH will display a big,
scary warning about the encryption keys changed. SSH remembers information about a
host, and when you connect to the same machine and the information doesn't match, it
displays a warning to indicate that there may be a "man-in-the-middle"
security attack going on. When you see this, you should verify that the server
really did change and then update your "known_hosts" file (delete the now-obsolete line).
You can think of this as a way to notice when the server move has happened.
Obviously if the data moves from server to server often, this will become annoying,
making the technique less useful.

########################################

[172]  About middle of page

aliases.done: $(PDIR)/aliases.pag $(PDIR)/aliases.dir
->
aliases.done: $(PDIR)/aliases.pag $(PDIR)/aliases.dir
	touch $@

and

access.done: $(PDIR)/access.dir $(PDIR)/access.pag
->
access.done: $(PDIR)/access.dir $(PDIR)/access.pag
	touch $@

########################################

{175} line 1, line 4, line 5 

$*
->
$@

(three occurrences)

########################################

{175} code example, line 1

args=`getopt ab: $*`
->
args=`getopt ab: -- "$@"`

########################################

{177} code example, line 1 

args=`getopt da:c:h $*`
->
args=`getopt da:c:h -- "$@"`

########################################

{181} second code example

$ sudo tcpdump -l -n arp | grep 'arp who-has'| head -100
->
$ sudo tcpdump -l -n arp | head -100 | grep 'arp who-has'

########################################

{183} code in middle of page

$ sudo tcpdump -l -n arp | egrep 'arp who-has' | head -100 | awk '{ print $NF }' |sort | uniq
-c | sort -n
->
$ sudo tcpdump -l -n arp | head -100 | egrep 'arp who-has' | awk '{ print $NF }' |sort | uniq
-c | sort -n

########################################