One reason why I like Unix
; uptime 19:33:45 up 264 days, 12 min, [...] ; ps -e -o start,comm STARTED COMMAND Feb 01 init [...] Feb 01 X Feb 01 xterm Feb 01 fvwm2 Feb 01 wish8.4 Feb 01 exmh [...] Apr 12 ssh [...]
I don't think long uptimes are an exclusive Unix virtue; every operating system can and should have them. But there's machine uptime and then there's total user environment uptime, and my impression is that many systems today are far less good at the latter.
Not only has has my office workstation and its system programs been running since February 1st, but I've been logged in and running X Windows continuously since then, along with my window manager, my mail reader, and several other programs that I keep running all the time. I use the machine reasonably intensely; I routinely compile large programs, watch video, play music, and so on.
The ssh command started April 12th has been forwarding X for my environment on the remote machine (which has obviously been up since then; in fact it was rebooted then), and that environment has been running since then:
; ps -o start,command [...] 12Apr05 xrun [...] 12Apr05 xlbiff -title [...]
It is very nice to just be able to expect this kind of quiet, long-term operation from everything that I run; it makes the computer my servant, instead of me the computer's servant ('I am annoyed with life; quit some of your programs to make me happy').
(Now, mind you, I am out of touch with the Microsoft Windows world; it is quite possible that multi-month Windows sessions are now perfectly normal if you want to stay logged in that long. Data points from Windows people are welcome.)
(The observant will gather from this that I have not installed Fedora Core 4 on my office workstation. Surprise, surprise. At this point I may wait for Fedora Core 5, unless I get impatient with outdated software.)
Weekly spam summary on October 22nd, 2005
This week we received 11,880 email messages from 233 different IP addresses. Our SMTP server handled 36,465 sessions from 4,042 different IP addresses, down markedly from last week.
Overall connections are down slightly from last week: 210,400 connections from at least 38,800 different IP addresses. This week, we only hit a highwater of 22 connections being processed simultaneously. Per day statistics:
The Sunday surge is expected; we reboot with much of the kernel level IP filters cleared, and active IPs to block hit us and get added back in later on in the day. Simultaneous connections being processed hit 13 on Sunday then 22 on Thursday.
Kernel level packet filtering top ten:
Host/Mask Packets Bytes 22.214.171.124 21081 1180K 126.96.36.199/24 11764 599K 188.8.131.52 9605 461K 184.108.40.206 6461 329K 220.127.116.11 6442 301K 18.104.22.168 5568 267K 22.214.171.124 5414 260K 126.96.36.199/24 5238 242K 188.8.131.52 4650 223K 184.108.40.206 4523 211K
No large netblocks made the list at all, but 220.127.116.11, 'Surge
really living up to its name (and reappears from
last week). Also putting in return appearances are
18.104.22.168, both getting kernel level
blocks due to repeated bad
It's been a good (or bad) week for DNS blocklists; 22.214.171.124 is
DSBL-listed, 126.96.36.199 is CBL-listed, and 188.8.131.52 is on the
ORDB. The remaining four IP addresses got blocked for repeated bad
Connection-time rejection stats:
23648 total 10554 dynamic IP 7333 bad or no reverse DNS 2369 class bl-cbl 832 class bl-spews 533 class bl-dsbl 367 class bl-sbl 336 class bl-ordb 211 class bl-njabl 169 class bl-sdul 5 class bl-opm
Unlike last week, there is no single really active sources.
|what||# this week||(distinct IPs)||# last week||(distinct IPs)|
Spammers are probably forging us less, although they continue to forge us. They will probably continue to forge us until the Internet melts down in a combination of depeerings, bankruptcies, and disagreements over which organization and country should run the whole thing.