Thanks for the incantation -- we will be turning off roaming profiles.
Even so, it still seems that smbd takes *way* too many cpu cycles
-- it should be more network and/or disk bound than cpu bound -- at
least
thats my experience with nfsd. Maybe something is misconfigured
with smbd on our
I think I have narrowed down the problem why smbd processes are soaking
up so much CPU on our file server. Here are some selected samples from
strace output as I attached to the offending smbd process:
Culprit #1
I took three sample snapshots, each lasted for several seconds, and I
took them
We have a Linux file server for a set of computer science and
engineering
labs where each lab contains machines running Mac OS X, Ubuntu Linux,
or some incarnation of Windows. At times the these machines become
almost unusable and I think I have narrowed the problem to smbd
processes
soaking
