From owner-freebsd-stable@FreeBSD.ORG Sun May 29 18:09:54 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A155616A41C for ; Sun, 29 May 2005 18:09:54 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from viefep14-int.chello.at (viefep14-int.chello.at [213.46.255.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C438543D1F for ; Sun, 29 May 2005 18:09:53 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from [80.98.207.149] by viefep14-int.chello.at (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050529180951.XZNL7053.viefep14-int.chello.at@[80.98.207.149]>; Sun, 29 May 2005 20:09:51 +0200 Message-ID: <429A056D.6040100@t-hosting.hu> Date: Sun, 29 May 2005 20:09:49 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <4298A622.3020100@t-hosting.hu> <20050528174949.GA48170@xor.obsecurity.org> <4298DA78.3020504@t-hosting.hu> <20050528213145.GA68641@xor.obsecurity.org> In-Reply-To: <20050528213145.GA68641@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: Abort rap from cron X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 18:09:54 -0000 No, I don't have anything in syslog, but I've relaized, when I run make, these errors happen more often. You mentioned, there this is a common problem on SMP systems when one start more processes simultaneously, but it is a single processor system. Might this error also exist on single processor systems? Gábor >OK, some binary is probably calling abort() explicitly then. You >should have a record in your syslog. > >Kris > >