From: Veit Wahlich (cru_at_legalized.de)
Date: Mon 20 Sep 2004 - 18:38:50 BST
Also Samba smbd (here 2.2.7 from RH9 distribution) is somewhat
problematic when run inside a VServer:
>From time to time Windows clients hang for several (about 3) minutes
when accessing files, supposable more frequently when sharing files.
I traced back this problem to smb oplock code where IP inter-process
communication is rejected because the source address is not 127.0.0.1.
This is hardcoded.
Working around is possible by either patching the hardcoded address or
by disabling oplocks completely, which might result in a performance
break down as oplocks allow aggressive client-side caching.
Oplocks can be globally disabled in the smb.conf by setting 'level2
oplocks = No', 'oplocks = No' in the [global] section.
We have also another smbd that is accessed by just 2 Linux clients,
where no such problems ever appeared although oplocks are permitted.
So until now I have not figured out whether this is because of the low
count of clients, because there was no concurrent access to the same
file or maybe Linux 2.4 smbfs simply does not support oplocks...
With best regards,
Vserver mailing list