From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 03:54:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E08B116A4CF for ; Sun, 7 Nov 2004 03:54:19 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B89543D45 for ; Sun, 7 Nov 2004 03:54:19 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from 192.168.1.1 (localhost [127.0.0.1]) with ESMTP id AE6592954C1; Sat, 6 Nov 2004 22:54:18 -0500 (EST) Received: from 192.168.1.199 (SquirrelMail authenticated user mikej); by 192.168.1.1 with HTTP; Sat, 6 Nov 2004 22:54:18 -0500 (EST) Message-ID: <1037.192.168.1.199.1099799658.squirrel@192.168.1.199> In-Reply-To: <20041107033204.GA5512@dan.emsphone.com> References: <20041107033204.GA5512@dan.emsphone.com> Date: Sat, 6 Nov 2004 22:54:18 -0500 (EST) From: "Mike Jakubik" To: "Dan Nelson" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com cc: Zoltan Frombach cc: freebsd-current@freebsd.org Subject: Re: portupgrade -af on FreeBSD 5.3 and I get two conftest signal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 03:54:20 -0000 Dan Nelson said: > In the last episode (Nov 06), Zoltan Frombach said: >> I've recently migrated to FreeBSD 5.3. I just upgraded my system to >> the brand new 5.3-RELEASE version, and first of all, I have to tell >> you that it works really great!! I love it! Thank you guys for the >> great work!! >> >> But I run into a somewhat weird problem. After the successful >> migration to 5.3-RELEASE from a previos 5.2-CURRENT version, when I >> recompile all installed ports with 'portupgrade -af', I get this in >> my system log file: >> >> Nov 6 16:59:54 www kernel: pid 8927 (conftest), uid 0: exited on signal >> 12 (core dumped) >> Nov 6 17:14:16 www kernel: pid 2733 (conftest), uid 0: exited on signal >> 12 (core dumped) >> >> But portupgrade proceeds and seemingly re-compiles all installed >> ports anyway (at least this is what I believe). When I look for the >> .core file(s), I can't find any on my hard drive anywhere! If the >> core was really dumped, then where did the .core files go? And how >> can I find out which port(s) are causing these problems? What is this >> signal 12 with conftest means anyway? I couldn't find anything about >> it by Googling... > > #define SIGSYS 12 /* non-existent system call invoked */ > > This is an unusual error to be getting, but it's possible that one of > the ports you tried to install tried to check for a syscall that either It's apache, i get these too.