From owner-freebsd-current Wed Oct 21 17:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04119 for freebsd-current-outgoing; Wed, 21 Oct 1998 17:38:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04095 for ; Wed, 21 Oct 1998 17:37:59 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA21346; Thu, 22 Oct 1998 10:07:28 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA01449; Thu, 22 Oct 1998 10:07:27 +0930 (CST) Message-ID: <19981022100727.C1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 10:07:27 +0930 From: Greg Lehey To: dg@root.com Cc: FreeBSD current users Subject: inetd still dying (was: cvs commit: src/sys/cam/scsi scsi_da.c src/sys/i386/i386 busdma_machdep.c vm_machdep.c src/sys/i386/ibcs2 imgact_coff.c src/sys/i386/include param.h src/sys/i386/isa isa.c wd.c src/sys/kern imgact_elf.c sys_pipe.c sysv_shm.c vfs_b References: <199810131154.EAA12696@implode.root.com> <19981014071356.S21983@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981014071356.S21983@freebie.lemis.com>; from Greg Lehey on Wed, Oct 14, 1998 at 07:13:56AM +0930 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 14 October 1998 at 7:13:56 +0930, Greg Lehey wrote: > On Tuesday, 13 October 1998 at 4:54:04 -0700, David Greenman wrote: >>> On Tue, 13 Oct 1998, David Greenman wrote: >>> >>>> dg 1998/10/13 01:24:45 PDT >>>> Log: >>>> Fixed two potentially serious classes of bugs: >>> >>> David, I'm having the inetd type problem on a system I can't bring to >>> current, it's using a kernel from back in August, but I was wondering if >>> it might be worth my while to see if these changes might possibly >>> backport that far, without breaking other things. Could I get your >>> non-binding guess on that, would it be worth my time to see if I could >>> do that? >>> >>> It's the problem that seems to be caused by starvation. >> >> It shouldn't be too difficult to port the changes to an August kernel. It >> is possible that this commit might fix the problem, but I'm fairly skeptical. >> It would probably be wise to wait and see if someone who is running up-to-date >> -current and was having the inetd problem can do some testing >> first. > > I've been having the problem, but only every couple of days. It still > existed yesterday. I'll report if it happens again. It happened again. I put inetd into gdb, but I couldn't find a way to resolve library addresses. It works if I start a program, but apparently not if I attach to it. Can anybody give me some pointers (like how to find the load address of a library)? This is a real -current but still using a.out binaries. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message