Samba 2.0.7 mem leaks, continued

Teemu Junnila (QRA) Teemu.Junnila at
Mon Sep 4 11:50:42 GMT 2000

Unfortunately, my samba processes are controlled by Veritas Cluster. It could off course be possible to break them out from the cluster and use inetd.conf, but the system serves several thousand users and has not one but several simultaneous logical nmbd/smbd services per one physical machine.
I think I keep on killing and starting the processes at nigth via cron untill a real fix/patch is done.

Teemu Junnila

-----Original Message-----
From: Neil Hoggarth [mailto:neil.hoggarth at]
Sent: den 4 september 2000 12:31
To: acherry at
Cc: samba-technical at; Teemu Junnila (QRA)
Subject: Re: Samba 2.0.7 mem leaks, continued

On Sat, 2 Sep 2000 acherry at wrote:

> ... but it appears to suggest a leak in the config file reloading
> code ...

One small observation: Based on Andrew's description, it sounds like
both affected sites might be able to temporarily work around their
problem by running smbd out of inetd, rather than as a standalone
daemon, on their production servers? That way you get a fresh smbd
process, which only ever parses the config file once, for each new

I use Samba 2.0.7 on Solaris 2.6 without problems, and it so happens
that I'm using inetd style, which might explain why I've not seen the
memory leak symptoms here.

Neil Hoggarth                                 Departmental Computer Officer
<neil.hoggarth at>                   Laboratory of Physiology                  University of Oxford, UK

More information about the samba-technical mailing list