Date: Sat, 27 Feb 2010 17:33:58 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Dan Naumov <dan.naumov@gmail.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: 8.0 on new hardware and a few errors, should I be worried? Message-ID: <20100228013358.GA70119@icarus.home.lan> In-Reply-To: <cf9b1ee01002271728m63e38793v6dab84283cab9914@mail.gmail.com> References: <cf9b1ee01002271728m63e38793v6dab84283cab9914@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 28, 2010 at 03:28:48AM +0200, Dan Naumov wrote: > Additionally, while building a whole bunch of ports on this new system > (about 30 or so, samba, ncftp, portaudit, bash, the usual suspects), I > noticed the following in my logs during the build process: > > -------------------------------------------------- > Feb 27 21:24:01 atombsd kernel: pid 38846 (try), uid 0: exited on > signal 10 (core dumped) > Feb 27 22:17:49 atombsd kernel: pid 89665 (conftest), uid 0: exited on > signal 6 (core dumped) > -------------------------------------------------- This is intentional/normal, believe it or not. It's by-design as part of some compiler tests that autoconf (or the software that uses autoconf) induces. Thanks, GNU! FreeBSD logs these to the console by default; the sysctl to control this behaviour is kern.logsigexit. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100228013358.GA70119>