On Tue, 12 Jun 2007, Carl Brewer wrote:
>> Yes, it's fixed in 4.0 and -current (though there has been the suggestion 
>> that there is a still a remaining memory leak somewhere).
>> 
>> The way to easily spot the telldir problem is to look at the smbd memory 
>> usage while hitting F5 in a Windows Explorer window (Refresh) which is 
>> viewing a Samba share. It'll increase every time you hit F5.
>
> Yep, we ran the app (AutoDESK) and it reported a failure when smbd (via
> ps) reported :
>
> USER    PID %CPU %MEM    VSZ   RSS TTY   STAT STARTED     TIME COMMAND
> todd    318 17.1 25.8 133576 132996 ?     S     9:19AM  0:31.15 
> /usr/pkg/sbin/smbd -D
>
> My guess is that that ran into the 128MB process limit by default in
> NetBSD 3.1.

Yes.

> Restarting samba 'fixed' it, as you'd expect.
>
> As a short term workaround I can bump up the memory limit for smb and
> restart smb every 'while' (for some hopefully sufficiently short 'while'
> that will make a difference) while waiting for 4.0 (or a patch to 3.1
> or your fix being pulled up into 3.1 stable? who do I grovel to?).  Any
> other suggestions?

You can probably grovel to me :-)

> btw, what's the cvs tag for 3.1 stable? is it 'netbsd-3' ?

That's right.

-- 
Stephen