This particular problem is driving me nuts. We use a Clearcase derivative called Accurev for source control and we are controlling Linux code with it. Our house network is Microsoft Exchange Server, so that is where the Accurev database is stored. When I host the workspace on Exchange Server, we have negligible latency (3 seconds or so for a workspace update)
But when I try to host the workspace on Linux, the same update takes 75 seconds. Every single operation except just reading a text file from the workspace takes an enormous amount of time. I got a copy of the smb.conf file from a techie at Accurev and compared it to mine. The only difference was that his had this line in it:
I compared my smb.conf file to yours and they were identical except that I didnt have this line in it:
passdb backend = tdbsam
We have SELinux completely disabled and access our shares by IP address rather than by name, so I dont think samba passwords matter.
We do not have to enter passwords to access the shares. So whether we have used passwd or tdbsam doesnt seem important.
Our samba shares are completely open: "security = share" is the most of what's in there other than just specifying the base folders for the shares.
But I added that line to my smb.conf file and restarted samba anyway and saw no difference.
Accurev is disavowing any responsibility for the slowdown, saying that the fault MUST be with Linux and Samba. They also claim that no one else has this problem and MANY of their customers are using samba-hosted workspaces.
I have tried this with Fedora 5, CentOS 5.0 and CentOS 5.3 and have had virtually the same results.
Is it likely that the tdbsam option could be a meaningful difference?
If I wanted to use tdbsam instead of passwd, what would I have to do?
Since I don't explicitly have to enter passwords to access the shares, and have SELinux disabled, doesn't that eliminate it as a candidate for blame?
Any suggestions for fixing this problem would be welcome. Without being able to host workspaces on the machines on which we do our compiles, it makes effective source control much harder to enforoce.
