From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Wed 22 Sep 2004 - 18:07:34 BST
On Wed, Sep 22, 2004 at 05:46:20PM +0200, Thomas Weber wrote:
> On Mon, Sep 20, 2004 at 07:38:50PM +0200, Veit Wahlich wrote:
> > Hi List!
> > 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.
> So this is still a problem. I had the same problem in a small network (~10
> windows clients) at least a year ago (think i reported it to the list also).
> It's a locking problem, quite easy to trigger: just try to access a word
> file from 2 clients. My solution at this time was to run the smbd from
> outside the vserver but chrooted - ugly, but it did (and still does) what
following the lkml, samba has more than one issue with
oplocks, but in this case it is probably simple to cure
by 'replacing' the 'check' for 127.0.0.1 by a check for
a configurable? ip ...
relying on 127.0.0.1 being localhost (and especially the
reverse) isn't such a good idea, nevertheless this will
go away in the near? future with 1.9.x (x>3 ?)
thanks for the info, maybe somebody could add it to the
list of problematic programs?
> I needed in this case.
> (RH8, 2.4.2x kernel, samba 2.2.x - whatever came with RH8)
> Vserver mailing list
Vserver mailing list