Date: Sat, 9 Sep 1995 14:51:22 -0400 (EDT) From: John Capo <jc@irbs.com> To: archive@cps.cmich.edu (Mail Archive) Cc: davidg@Root.COM, roberto@keltia.freenix.fr, freebsd-current@freebsd.org Subject: Re: sig 11 Message-ID: <199509091851.OAA16895@irbs.irbs.com> In-Reply-To: <Pine.SUN.3.91.950909143240.20036A-100000@cps201> from "Mail Archive" at Sep 9, 95 02:35:11 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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 > > > > I brought in the sed SCO compatibilty changes from -current, and this may > > be related. If this is the case, I will back out the changes (I don't have any > > time to troubleshoot the problem). > > Let us know if you see any other programs dieing this way. Thanks. > > > With sup'ed to -current on two machines (Tuesday sept5 was the sup date) > and after make worlds on both of them we get the Exact same problem with > Sig 11. Since the start of Sig 11's my boss wants us to move back to > Debian Linux. I would perfer just to resup and recompile and get this > fixed and not have to restart the machines from scratch. > 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. John Capo IRBS Engineering
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509091851.OAA16895>