Limiting how much load Exim puts on your system
One of the things that you usually want to do with MTAs is have somelimit on how many things that they'll try to do at once. This isespecially important if, like us, you allow users to run programs fromtheir .forward s; people do every so often have runaway programs, orjust programs that sit there endlessly (trying to get a lockfile, forexample).
Unfortunately, Exim only has limited support for load limiting. Whatyou really want to do is limit the number of
喜讀桑內特
兇狠
昨天一早沽的期指整天沒甚變動，相信今天是收成期 。
前天晚上 沽 期金，嚇到癡肺，因為個市是這樣（spot and futures有點分別，但勢頭是一樣）：
期金：金升$1，我輸US$10
Combining dual identity routing and isolated interfaces revisited
Back in DualIdentityIsolation , I described how I set up a dualidentity machine so that it had isolatedinterfaces . In it I wrote:
Alas, I am now left with a mystery: according to the policy routingrules, it looks like a packet from IP1 to an address on that subnetshould get routed via the gateway (and similarly for the othernetworks), [....]
You know what? I should have paid more attention to the mystery,because as it turns out such packets were
歌詩吧漫遊 Gili Gulu 2
歌詩吧漫遊 Gili Gulu 2
烽火台是抗爭地，連結左中右
引文：
中大校方拆卸烽火台的決定，由頭到尾都是黑箱作業。學生、校友甚至教職員，竟然都是在傳媒揭發後才知悉整個計劃。校長更稱「這些工程傳統上不公開諮 詢教
A growing realization about tcpdump and reading IP traffic
Here is a gotcha about reading tcpdump output that recent events havebeen tattooing on my forehead:
The only sure way to tell whether a packet is going to your gatewayor to something on the local network is to look at the destinationEthernet address.
To put it another way: a packet being sent to your network's gatewaydoes not have the gateway's IP address in it. Thus, reading tcpdump output without Ethernet addresses is not really telling you whether apacket was really sent to your gateway or whether
BitTorrent's file fragmentation problem
When BitTorrent receives a file, it gets the various chunks out of order, generally in a completely randomone. This presents the client with the problem of putting them inorder and in place.
I believe that historically there have been three approaches to dealwith this. The very first BitTorrent clients did it the simple way:they put every received block in its correct place by seeking to thatspot and writing the block out. The problem with this was horrible filefragmentation (resulting in terrible sequential read performance);
