This is a two part safety tip:

1. most things that roll Apache logfiles SIGHUP Apache to get it toclose and reopen the logfiles
2. when Apache is SIGHUP 'd, it closes its current set of sockets andtries to listen on the set that its configuration file says itshould use.

So, if you have changed Apache's configuration of what it should listenon, and something else is currently camped on one of those places,something that is scheduled to be killed off during an impendingreboot, and your logfiles

The basic volume numbers for this week are that we:

• got 19,744 messages from 236 different IP addresses.
• handled 19,083 sessions from 955 different IP addresses.
• received 139,156 connections from at least 43,459 different IPaddresses.
• hit a highwater of 31 connections being checked at once.

We got more emails this week than usual mostly because of a small mailloop explosion during the week that added several thousand

For my sins, I am one of those people who doesn't always read Python'sfine documentation carefully enough. For example, I wrote a large chunkof code using the helpful os.path.join() before I noticed a littlegotcha: it's very helpful. In particular:

Joins one or more path components intelligently. If any component isan absolute path, all previous components are thrown away, andjoining continues .

(Right there in black and white in the fine documentation .)

There's three ways to build RPMs: the silly way, the easy way, andthe better way.

The silly way starts with /bin/su root , which should be enough of a warning sign. You really don't wantto be building and installing packages as root unless you don't have achoice, and you do.

The easy way is:

$ cat >$HOME/.rpmmacros
%_topdir /some/where
^D
$ cd /some/where
$ mkdir BUILD