This week, we:

• got 11,905 messages from 252 different IP addresses.
• handled 27,710 sessions from 2,367 different IP addresses.
• received 342,122 connections from at least 124,401 different IPaddresses.
• hit a highwater of 36 connections being checked at once.

Connection volume seems up a bit from last week ,although it's hard to be entirely sure. Session volume is definitelyup,

I'm in the process of getting a new test server installed in a rackin our machine room. This means we needed to set up some networkconnections for it, which involved someone dragging yet more cablearound our machine room and finding switch ports to plug into to getthe necessary networks (which turned out not to be an entirely trivialthing).

As a result, the whole thing got me thinking about the issue of the bestway to get all of your networks to where they need to be in

Here's a mistake I've made more than once:

tail -f active-log | grep big-filter | grep -v one-thing

(Here the big-filter is something that selects only a small amountof actual interesting logfile output, and then you want to throw awaya small bit more. For example, my most recent version of this wasmonitoring the exim log on our new mail system for failures and otheranomalies, and then wanting to throw away one particular known failure.)

Looking up reverse DNS to determine the hostname of an IP address thatyou are talking to is one of those almost simple things that softwarekeeps getting wrong .So here is how you do it, in two variants.

First, if you use DNS and have an (almost) empty /etc/hosts or justdon't care about looking up something in it, is the simple version:

• gethostbyaddr() the IP address. If it fails, you are done. Otherwiseyou have the claimed hostname .

  (