From owner-freebsd-current Fri Aug 7 13:03:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09211 for freebsd-current-outgoing; Fri, 7 Aug 1998 13:03:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA09197 for ; Fri, 7 Aug 1998 13:03:14 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0z4sfG-0000em-00; Fri, 7 Aug 1998 12:59:02 -0700 Date: Fri, 7 Aug 1998 12:59:02 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: Dusk Auriel Sykotik cc: freebsd-current@FreeBSD.ORG Subject: Re: memory leaks in libc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Aug 1998, Dusk Auriel Sykotik wrote: > Apache uses them quite frequently. And this could make it very costly on > large webservers. Where I work, we have hundreds of connections to some > of our webservers per minute. We also use cgi scripts very frequently, > and these use *env* functions quite frequently as well. Where exactly is Apache using getenv() and setenv() frequently? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message