Errata

Time Management for System Administrators

Errata for Time Management for System Administrators

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page x
6th paragraph

Author wrote:
"Most sysadmins can't repel down the side of a building..."

Author used the word "repel" rather than "rappel"

Anonymous   
Printed
Page x
4th line from the bottom of the page

Daniel Khodorkovsky reported (and I haven't confirmed)

Foreward, page x. 4th line from the bottom of the page
reads "repel down the side of a building."
The line should read "rappel down the side of the building."

Thomas Limoncelli
Thomas Limoncelli
 
Apr 19, 2014 
Section 13.3 the subhead "A Makefile for Every Host"

"Who has time to remember which command is used after which file is edited? Details like that are what computers are for."

Change "after which file" should be "after each particular file"

Note from the Author or Editor:
Please change as suggested.

Thomas Limoncelli  Aug 28, 2016 
Printed
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.

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

Anonymous    Mar 01, 2007
Printed
Page xxiii
Acknowledgements

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

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

Anonymous    Mar 01, 2007
Printed
Page 20
+1

20 attractions per hour
->
12 attractions per hour

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

Anonymous    Mar 01, 2007
Printed
Page 20
+1

dizzying three hours
->
dizzying five hoursi

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

Anonymous    Mar 01, 2007
Printed
Page 25
next to last paragraph in the box

"the customer is much more satisfied because she receives visual proof that I'm attending to his request"

The "she" should be "he".

Tom Limoncelli  Oct 29, 2010 
Printed
Page 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.

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

Anonymous    Mar 01, 2007
Printed
Page 34
3rd paragraph

Printed version is:
"It's a nice, simple routing that works for me."

This should be:
"It's a nice, simple routine that works for me."

Anonymous  Jul 04, 2010 
Printed
Page 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.

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

Anonymous    Mar 01, 2007
Printed
Page 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.)

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

Anonymous    Mar 01, 2007
Printed
Page 86
last bullet point

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

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

Anonymous    Mar 01, 2007
Printed
Page 130
"Delete or forward, then delete"

pg 130 (Ch 10, Email Management, "Delete or forward, then delete")

I also don't reply to emails spreading the latest hilarious Internet
joke - such as when I learned about a seven-year-old boy in England,
named Craig Shergold, trying to get into the _Guiness_Book_Of_World_
_Records_ by amassing the largest postcard collection. Oh wait, that's
an urban legend.

It isn't an urban legend; it is a real story that is no longer relevant because he made the record.

I would change:
Oh wait, that's an urban legend.
to
Oh wait, he's no longer collecting them.

Note from the Author or Editor:
I'm conflicted because while you are correct, my version reads better to someone that isn't "in the know".

I would ask O'Reilly to change it to "Oh wait, that's now just an urban legend."

Anonymous   
Printed
Page 133
5th paragraph

Daniel Khodorkovsky reported (and I haven't confirmed)

Chapter 11, page 133. 5th paragraph reads:
"...I decided to stop reading Usenet all together."

The line should read "...I decided to stop reading Usenet
altogether."

Thomas Limoncelli
Thomas Limoncelli
 
Apr 19, 2014 
Printed
Page 137
+2

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

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

Anonymous    Mar 01, 2007
Printed
Page 154
+3

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

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

Anonymous    Mar 01, 2007
Printed
Page 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

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

Anonymous    Mar 01, 2007
Printed
Page 165
code example in bold, line 3

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

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

Anonymous    Mar 01, 2007
Printed
Page 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.

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

Anonymous    Mar 01, 2007
Printed
Page 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 $@

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

Anonymous    Mar 01, 2007
Printed
Page 174
makeimage1 script example

http://www.oreilly.com/catalog/timemgmt/errata/timemgmt.307 states:

> ########################################
>
> {175} line 1, line 4, line 5
>
> $*
> ->
> $@
>
> (three occurrences)
>
> ########################################

pg 175, line 1, (corrected) thus reads:

> The $@ in the makeimage1 script...

The other two occurrences cited in the above correction likewise refer to the same script (bottom of 174).

However, while the description of the makeimage1 script on 175 was updated in 3/07, the script itself was not updated, and still reads:

> mkisofs _D -l -J -r -L -f -P "Limoncelli" -V `date -u %m%d` $*

The "$*" at the end of the script should, it would therefore seem, be changed to "$@", in keeping with 3/07 {175} line 1, line 4, line 5. (The same error appears to have also been corrected in 3/07 {175} code example, line 1 and 3/07 {177} code example, line 1.)

Anonymous   
Printed
Page 175
Paragraph before the script, line 5 and 6

The getopt described there and used in the following example is not a bash
function/built-in; see http://software.frodo.looijaard.name/getopt/ for details.

Anonymous   
Printed
Page 175
line 1, line 4, line 5

$*
->
$@

(three occurrences)

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

Anonymous    Mar 01, 2007
Printed
Page 175
code example, line 1

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

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

Anonymous    Mar 01, 2007
Printed
Page 177
code example, line 1

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

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

Anonymous    Mar 01, 2007
Printed
Page 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'

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

Anonymous    Mar 01, 2007
Printed
Page 182
in code sample

Yiorgos Adamopoulos sent me email saying that on his copy, page 182 lists:

sudo tcpdump -l -n arp | head -100 > /tmp/x | grep 'arp who-has'

but the correct code is:

sudo tcpdump -l -n arp | grep 'arp who-has' | head -100 > /tmp/x


The printed copies that I have at home look correct. Maybe this error was introduced in a new printing?

--Tom Limoncelli (author)

Thomas Limoncelli
Thomas Limoncelli
 
Nov 08, 2008 
Printed
Page 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

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

Anonymous    Mar 01, 2007