From owner-freebsd-current Fri Oct 9 10:58:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15008 for freebsd-current-outgoing; Fri, 9 Oct 1998 10:58:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA15003 for ; Fri, 9 Oct 1998 10:58:33 -0700 (PDT) (envelope-from alk@East.Sun.COM) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id KAA07720 for ; Fri, 9 Oct 1998 10:58:24 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id NAA16371; Fri, 9 Oct 1998 13:58:21 -0400 Received: from east.sun.com (hobo192 [129.148.7.192]) by suneast.East.Sun.COM (8.8.8+Sun/8.8.8) with ESMTP id NAA02678 for ; Fri, 9 Oct 1998 13:57:39 -0400 (EDT) Received: (from alk@localhost) by east.sun.com (8.9.1/8.7.3) id MAA01181; Fri, 9 Oct 1998 12:55:47 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 9 Oct 1998 12:55:47 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: inetd is ill? syslogd is anemic? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13854.19308.314677.685227@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been occurring for almost a week -- of a sudden, I get a few hundred of these: Oct 9 12:30:22 avalon /kernel: pid 756 (inetd), uid 0: exited on signal 11 Oct 9 12:30:22 avalon /kernel: pid 757 (inetd), uid 0: exited on signal 11 Oct 9 12:30:22 avalon /kernel: pid 758 (inetd), uid 0: exited on signal 11 Oct 9 12:30:22 avalon /kernel: pid 759 (inetd), uid 0: exited on signal 11 This particular instance is from a Wed 7 Oct 1:32 cvsup/buildworld/kernel in an ELF/SMP world. It seems to relate to alk 10629 0.0 29.7 119272 18652 v0 I 7:56PM 18:07.71 netscape-4.0.7 memory leaks in other things. But there's more to the story than that, because I just killed that netscape, and with 12:50PM up 2 days, 11:10, 4 users, load averages: 0.31, 0.22, 0.13 Virtual: 67504K; Resident: 14331K (37.9% of available) Swap: /dev/sd0s1b 131072 28692 102252 22% Interleaved I subsequently got a few hundred more: Oct 9 12:50:20 avalon /kernel: pid 1137 (inetd), uid 0: exited on signal 11 Oct 9 12:50:20 avalon /kernel: pid 1138 (inetd), uid 0: exited on signal 11 Oct 9 12:50:20 avalon /kernel: pid 1139 (inetd), uid 0: exited on signal 11 Oct 9 12:50:20 avalon /kernel: pid 1140 (inetd), uid 0: exited Oct 9 12:50:20 avalon /kernel: pid 1141 (inetd), uid 0: exited on signal 11 I hazard that this also illustrates a problem with the syslog facility not quite cutting it under stress. A lonely laggard just came in: Oct 9 12:53:40 avalon /kernel: pid 1171 (inetd), uid 0: exited on signal 11 Something funny about comsat? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message