Hello again,
I will hijack this thread with one more post only because I said I would post the results from using the patched fam package.
I installed the new fam package from dropline on my server (slackware-10.2 - 2.4.31 - no Gnome) and started it up.
I did not at first think there was much difference.
For those who are interested (god help you
) fam, running on the client, will attempt to use famd running on the server. If it cannot, it will drop back to polling at an interval set from one of several config files on the client depending on how fam is started on the client. The default is every 6 seconds supposedly, but I can assure you that what I have been experiencing seems like over 6 times per second. I have seen a number of posts during my search that indicated a small network has been brought to it's knees as a result of this behavior. I believe that /home directories were being exported via NFS in these cases. [0]
My client box has slackware 10.2 with 2.4.31, slackware 10.2 with 2.6.13, and SuSE-10.0.
The 2.6.13 slack install, which I am using mostly now, automounts the NFS share at boot via fstab. An icon is created in Gnome on the desktop automagically and browsing the share from this icon does not cause the hammering of my server now as it used to! If I browse any of the directories further down the tree though my server gets hammered again. So a slight improvement there.
What is odd is this. I have a number of symlinks in my home directory that point to these same files that cauuse the hammering mentioned above. If I browse these directories via the symlinks, I get no hammering. This is new and a big improvement.
I am of the opinion that my configuration is to blame to some degree, but evrything looks ok.
So thats it. I will keep playing and maybe post a success story sometime.
Thanks for the help zborgerd and when I have more time I may post to the dropline forums. Just no time with the holidays and work.
Steve
[0] I admit to only vaguely understanding this