We've recently been having a problem where one specific clientexperiences really slow IO to one specific NFS mounted filesystem,especially for things like file creation. (Other clients can use thefilesystem at full speed, and this client can use other filesystems atfull speed.)

We immediately thought 'per-filesystem concurrency limits'and soon turned up the Solaris 8 NFS kernel tunable nfs3_max_threads , which the fine documentation helpfullydescribes as:

This symbol controls the maximum number of async threads started perfile

One of the few things that keeps me running while I am only ondialup is ' yum localupdate '. With a combination of' yum check-update ' and ' yum localupdate ' I can get a list ofwhat RPMs I need to update, pull down copies of those RPMs atwork, dump them onto a USB key ,take them home, and then update them locally.

In theory.

In practice, ' yum localupdate ' seems to sometimes ignore RPMsthat I've supplied on the command line if

Dear Xine: since various modern sound systems are amply equipped toplay multiple audio sources at once, your 'mute' button should muteonly your audio, not the entire audio chain. That way I can turn downthe Internet music stream I'm listening to in the background in favourof something of more immediate interest, like YouTube videos, withouthaving to quit out of you entirely.

While we're here, it would be nice if you didn't block purely audiostreams just because you can'

In dump (and ufsdump, and other close cousins) you can specify thefilesystem that you want to dump in two ways: by the name of itsmountpoint, or by the name of the (raw) device that it's on. One ofmy little twitches is that I always specify thefilesystem to dump by its mountpoint. Like a lot of my little twitches,this has a history behind it.

The problem is that at least some old versions of dump were perfectlywilling to write their output to