Today's excitement came from trying to bring a local network daemonfrontend up and running on a FreeBSD machine. It would spawn programswhen you connected to it, but they always exited immediately afterthey printed their greeting banner; it was as if they were seeing animmediate end of file.
FreeBSD's ktrace revealed that when the spawned programs went toread from standard input, they got an EAGAIN result. Fortunately I'vestubbed my toe on this one before: this is the exact symptom of yourstandard
Recently, Intel and AMD have been telling everyone who would listenthat single CPU performance is more or less all tapped out, and thatfuture improvements would come from various multi-* developments;multi-core, multi-processor, and so on. Ominous pronouncements haveemerged about how programmers need to bite the bullet and move to(highly) concurrent programming if they want their gravy train tocontinue.
When reading this sort of news coverage, it's worthwhile to rememberwhat sells CPUs and software. Namely:
New
Google Video
Our Media
Vernon Schryver, in news.admin.net-abuse.email:
Spam complaints must be viewed like complaints from your neighborsthat your children or other pets have again wrecked gardens. Spamcomplaints are evidence of failures, and should be exceptionsinstead of part of the main anti-spam machinery.
(From Message-ID <95cqle $80v$1@calcite.rhyolite.com> .) One of the things I've learned the hard way in writing Unix programsis that you should almost never expect to know all of the errno valuesthat system calls can return. In theory it's documented in themanpages, but in practice a manpage's list is never comprehensive.The safest thing to do is to assume that any system call can returnalmost any errno value. The example I remember most vividly is that our SMTP server daemonused to carefully check the result of
The danger of specific errno values
accept() . If
答留言．薦書
前文見此
暉：
你說的話我並不完全反對。確然很多人都將韓農想像成受難者，好像他們不是受難者，或者有更苦的受難者，韓農就不值得支持。不過，我認為你也是抱持這種邏輯的人。否則，你發現中國農民比韓國農民更慘，那 Menu