From owner-freebsd-questions Sat Aug 10 19:49:19 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA02909 for questions-outgoing; Sat, 10 Aug 1996 19:49:19 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA02898 for ; Sat, 10 Aug 1996 19:49:16 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id TAA00446 for ; Sat, 10 Aug 1996 19:49:11 -0700 (PDT) Received: from stgenesis.org by mail.crl.com with SMTP id AA00388 (5.65c/IDA-1.5 for ); Sat, 10 Aug 1996 17:34:59 -0700 Received: (from freebsd@localhost) by stgenesis.org (8.6.12/8.6.12) id NAA20089; Sat, 10 Aug 1996 13:22:37 -0500 Date: Sat, 10 Aug 1996 13:22:36 -0500 (CDT) From: Leigh Gaffney To: Bill Cc: questions@freebsd.org Subject: Re: ircd recompile In-Reply-To: <1.5.4.32.19960810220245.006c4350@mail.nas.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 10 Aug 1996, Bill wrote: > > I had to recompile ircd (in order to disable operator password encryption, > and enable operator kills). > > I did a make on the ircd directory itself (where the server sources are). > > After the make was done, I noticed that the ircd executable was five times > larger in size than the one originally built when I installed the entire IRC > 2.8.21 port. > > Although ircd seems to be running fine, I can't help wondering why the > executable grew five fold. > > Any ideas? ircd as a whole is a pretty large program - dalnet is in the process of re-writting the code for ircd to compact it more. My understanding is that all of the ircd's are rather large. I dunno for undernet and efnet though, I'm most familiar with dalnet. But as a whole the ircd is large - just be worried if it runs at more than 20M in mem - that's the mem leak which ircd and 2.1.0 experience - least on the dalnet code (upgrade to 2.1.5 and it'll fix it for you) -Leigh