For a long time, one of my acquired articles of faith has been thatyou needed to worry about and avoid the thundering herd accept() problem. (This is the problem where ifyou have a bunch of processes all waiting in accept() and a singleconnection comes in, many kernels will wake all of the processes up onlyto have most of them immediately go back to sleep.)

One of the things that Unicorn (via Ryan Tomayko and others )has taught me about preforking servers is that the

It's nice that Sun has provided the OpenSolarissource in the form of a VCS repository , but inmany ways it's not terribly useful. The problem with it is that theOpenSolaris repo is not a working repository.

By that I mean that it is not what the Sun developers actually workin; instead it is essentially a series of code snapshots convertedto a repository. It's nice that we get a sequence of snapshots ina convenient form, and it's nice that it happens relatively

To follow up an earlier entry , one might sensibly askwhat the problem is with using a modern, whole-directory version controlsystem on a directory full of unrelated files, the classical examplebeing /etc .

What you effectively have in this situation is a directory with multiple'modules' (files and groups of files) that are logically separate andindependent from each other. As they're separate modules, these filesusually evolve and are developed at least somewhat independently.Putting all of these files into a single