Date: Sat, 09 Sep 1995 13:31:57 -0700 From: David Greenman <davidg@Root.COM> To: Mail Archive <archive@cps.cmich.edu> Cc: John Capo <jc@irbs.com>, roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: sig 11 Message-ID: <199509092031.NAA00235@corbin.Root.COM> In-Reply-To: Your message of "Sat, 09 Sep 95 16:07:18 EDT." <Pine.SUN.3.91.950909160635.22301A-100000@cps201>
next in thread | previous in thread | raw e-mail | index | archive | help
>On Sat, 9 Sep 1995, John Capo wrote: > >> Mail Archive writes: >> > >> > On Sat, 9 Sep 1995, David Greenman wrote: >> > >> > > ... >> > > >pid 123: sed: uid 8: exited on signal 11 >> > > >pid 126: sed: uid 8: exited on signal 11 >> >> These kinds of problems are all part of running -current. Current >> is a development tree and is quite often broken for one reason or >> another. Like the docs say, "The bleeding edge". >> >> Sounds like you should be running -stable rather than -current. >I have been compiling -stable for the last 4 hours it just finished >rebooted and got the EXACT same thing... > >You explain why it doesn't matter.... Okay, everyone else has reported back that the problems have gone away after rebuilding everything. The only remaining report of sig 11 type of trouble is yours. Can you send me more information about your system, a "dmesg" would be useful, for example. Also, when was the last time you updated your sources? It's possible that the update you did was during a time when changes were being made and thus the changes may be incomplete. -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509092031.NAA00235>