From owner-freebsd-current Fri Jan 8 05:39:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24501 for freebsd-current-outgoing; Fri, 8 Jan 1999 05:39:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24495 for ; Fri, 8 Jan 1999 05:39:41 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id OAA29693; Fri, 8 Jan 1999 14:38:40 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA03865; Fri, 8 Jan 1999 14:38:39 +0100 (MET) Message-ID: <19990108143839.G348@follo.net> Date: Fri, 8 Jan 1999 14:38:39 +0100 From: Eivind Eklund To: "T.D. Brace" , freebsd-current@FreeBSD.ORG Subject: Re: inetd problem References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from T.D. Brace on Thu, Jan 07, 1999 at 05:01:42PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 07, 1999 at 05:01:42PM -0500, T.D. Brace wrote: > > Hello, > > Can anyone tell me if the inetd realloc (and other) problems have been > fixed yet? Searching Deja News shows conflicting reports. I checked > the current diffs, and built version 1.46 - is this a safe version to > use? It's been running on my local workstation for a few days now, but > it really doesn't have any load on it. I'd like to copy it up to our > webservers, but thought I would ask first. 1.46 should be safe. It has a fix for the 'realloc' problem that does not rely on undocumented behaviour, and AFAIK works quite well. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message