How often have you seen a reverse DNS entry of host.dom.ain.10.11.12.in-addr.arpa. ? I've seen it too often, andI've even created them too often. Such incorrect reverse DNS entriesexist only because Bind makes it all too easy to shoot your foot off byinsisting on perfect consistency; for PTR records, as for all otherrecords, a name without a terminating dot is taken to be in the nameof the

When we set up strict overcommit mode , we hadto pick an overcommit ratio, or the alternate way of looking at it, wehad to pick how much total address space commitment we allow. Because wefirst did this for compute servers, we decided to size things so that anactive process would be able to use more or less all of the machine'sphysical memory, plus allow some extra on top to account for systemprocesses that would get pushed into swap.

The logic is relatively straightforward:

• on dedicated

This server recently moved from FedoraCore 2 to FreeBSD, and in the process I discovered that I had quietlybecome addicted to a few vim features, despite past dislikes of overly intelligent things that call themselves vi .

(I am pleased to report that the default FreeBSD version of vim does not behave that way .)

So it turns out to be necessary to set a few vim parameters to getit to behave the way I want. For my future reference, here's what I'vefound I need to

For reasons that do not fit into the margins of this entry, DWiki sometimes needs to get the current Unix load average. I developed DWiki on Linux, and getting the load average on Linux is really easy; you reada line from /proc/loadavg , split it into three floating point numbers,and you're done. So I wrote a get_load function that did that andforgot about the whole thing.

Then this server got changed from Linuxto FreeBSD, and suddenly that code didn't