Date: Thu, 25 Jan 1996 19:44:24 -0800 From: Joe McGuckin <joe@implode.Root.COM> To: hackers@freebsd.org, scrappy@ki.net Subject: Re: Program getting signal 11 for no obvious reason Message-ID: <199601260344.TAA08193@ns.via.net>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601260344.TAA08193>