Time-critical problem at Sun: exploding smbd memory usage
Richard Bollinger
rabollinger at home.com
Thu Aug 23 12:46:27 GMT 2001
Funny... I don't see the change in 2_2 CVS... did you really apply it?
Ahhh I see... Jeremy took it back out. Nice of him to do so, but I think he's wrong. The "main
loop" doesn't clean things up after each printer is added when we're using a [printers] clause in
smb.conf. That loop occurs inside pcap_printer_fn. Per my testing, this only seems to make a
difference on Solaris. Maybe fragmentation is occuring inside their malloc() free()?
Rich B
----- Original Message -----
From: "Gerald Carter" <gcarter at valinux.com>
To: "Richard Bollinger" <rabollinger at home.com>
Cc: <David.Collier-Brown at sun.com>; "Michael E Osborne" <mosborne at jacads.com>; <jeremy at valinux.com>;
<farrar at parc.xerox.com>; "Kris Desjardins" <kris_desjardins at hotmail.com>; <tonys at aus.sun.com>;
<craig at aus.sun.com>; <allenw at sun.com>; <samba-technical at samba.org>
Sent: Tuesday, August 21, 2001 9:56 PM
Subject: Re: Time-critical problem at Sun: exploding smbd memory usage
> On Tue, 21 Aug 2001, Richard Bollinger wrote:
>
> > Try the attached patch to fix the printer related leakage on Solaris.
> > We also have about 300 printers.
>
> Thanks! I've merge the missing lp_talloc_free() into
> lp_add_one_printer() for 2.2 and HEAD.
>
>
>
>
>
> cheers, jerry
> ---------------------------------------------------------------------
> www.valinux.com VA Linux Systems gcarter_at_valinux.com
> www.samba.org SAMBA Team jerry_at_samba.org
> www.plainjoe.org jerry_at_plainjoe.org
> --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
>
More information about the samba-technical
mailing list