From owner-freebsd-hackers Thu Jan 25 21:27:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA05752 for hackers-outgoing; Thu, 25 Jan 1996 21:27:37 -0800 (PST) Received: from ns (ns.via.net [140.174.204.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA05739 for ; Thu, 25 Jan 1996 21:27:29 -0800 (PST) Received: (from joe@localhost) by ns.via.net (8.6.9/8.6.9) id TAA08193; Thu, 25 Jan 1996 19:44:24 -0800 Date: Thu, 25 Jan 1996 19:44:24 -0800 From: Joe McGuckin Message-Id: <199601260344.TAA08193@ns.via.net> To: hackers@freebsd.org, scrappy@ki.net Subject: Re: Program getting signal 11 for no obvious reason Sender: owner-hackers@freebsd.org Precedence: bulk This sounds like what happened to me today. I just added an extra 32M of ram and rebooted. After a while, I started getting syslog messages about cgi scripts and httpd's dying of signal 11. Jan 25 14:19:01 ovation /kernel: pid 4760: perl: uid 65534: exited on signal 11 Jan 25 14:19:01 ovation /kernel: pid 4761: perl: uid 65534: exited on signal 11 Jan 25 14:19:44 ovation /kernel: pid 4775: perl: uid 65534: exited on signal 11 Jan 25 14:19:44 ovation /kernel: pid 4776: perl: uid 65534: exited on signal 11 Jan 25 14:20:23 ovation /kernel: pid 4795: perl: uid 65534: exited on signal 11 Jan 25 14:20:24 ovation /kernel: pid 4797: perl: uid 65534: exited on signal 11 Jan 25 14:20:33 ovation /kernel: pid 4799: perl: uid 65534: exited on signal 11 Jan 25 14:21:10 ovation /kernel: pid 4811: perl: uid 65534: exited on signal 11 Jan 25 14:21:21 ovation /kernel: pid 4822: perl: uid 65534: exited on signal 11 Jan 25 14:21:43 ovation /kernel: pid 4825: perl: uid 65534: exited on signal 11 Jan 25 14:22:30 ovation /kernel: pid 4843: perl: uid 65534: exited on signal 11 When I logged in, I couldn't run ls. I guess it has something to do with shlibs not working. -joe