From owner-freebsd-current Tue Jan 26 09:58:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07463 for freebsd-current-outgoing; Tue, 26 Jan 1999 09:58:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07458 for ; Tue, 26 Jan 1999 09:58:51 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id JAA05166; Tue, 26 Jan 1999 09:58:02 -0800 (PST) (envelope-from dhw) Date: Tue, 26 Jan 1999 09:58:02 -0800 (PST) From: David Wolfskill Message-Id: <199901261758.JAA05166@pau-amma.whistle.com> To: current@FreeBSD.ORG, des@flood.ping.uio.no Subject: Re: CALL FOR FEEDBACK: inetd In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Dag-Erling Smorgrav >Date: 28 Dec 1998 16:17:24 +0100 >I just committed a patch to inetd (rev. 1.44 of inetd.c) which I hope >fixes the "junk pointer: too low to make sense" bug mentioned in PR >bin/8183. I'd appreciate if those of you who have experienced problems >with inetd would tell me as quickly as possible if the patch >alleviates those problems. I realize that this note may be so late that it is anticlimactic... but the 3.0 machine here that had been exhibiting the above-referenced problems (typically, in conjunction with amanda backups) has resolutely failed to exhibit them since the inetd patch was installed. We believe that the machine has been exercised enough that the symptoms would have recurred had the problem(s) still existed. Thanks, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message