Every time I see a mail from a C/R system, I get more and more temptedto teach our mail filtering infrastructure about the most common ones,so that it can automatically acknowledge the challenges, discard themessages, and not bother the users with them at all.

Will this acknowledge a lot of spam, and thus dump it on the peopleoperating those C/R systems? Sure, but that's not our problem. AndI'd clearly be doing our users a service, especially if

This week, we:

• got 15,405 messages from 262 different IP addresses.
• handled 23,822 sessions from 1,467 different IP addresses.
• received 258,033 connections from at least 76,977 different IPaddresses.
• hit a highwater of 7 connections being checked at once.

The overall volume is about the same as last week ; technically it's up a bit, but I figure it'swithin the normal

On V7, UCB BSD 4.x, SunOS 2.x, 3.x and 4.x, the *BSDs, Linux, andanything using GNU fileutils:

; touch a b; ln a b && echo oopsln: b: File exists

On System V, including Solaris 8:

; touch a b; ln a b && echo oopsoops

That's right: the System V version of ln goes to significantextra work over just calling link(2) , and in