From owner-freebsd-current Wed May 13 16:24:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13311 for freebsd-current-outgoing; Wed, 13 May 1998 16:24:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13306 for ; Wed, 13 May 1998 16:24:51 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA08597; Wed, 13 May 1998 16:16:42 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd008577; Wed May 13 23:16:32 1998 Date: Wed, 13 May 1998 16:16:08 -0700 (PDT) From: Julian Elischer To: Alexander Litvin cc: current@FreeBSD.ORG Subject: Re: daemons exiting on signal 11 In-Reply-To: <19980513093110.21002@carrier.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I gather that means that make -j64 succeeded? On Wed, 13 May 1998, Alexander Litvin wrote: > I thought the problem has gone. But yesterday trying to test > new softupdates patches, I loaded my machine with 'make -j64 > buildworld', and at some point cron started to exit with SIGSEGV. > After makeworld finished problem with cron didn't disappear, > so I needed to restart cron :-\ > > Alexander Litvin > > --- > It's lucky you're going so slowly, because you're going in the wrong > direction. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message