From owner-freebsd-stable Tue Jun 15 12: 3:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id C259115617 for ; Tue, 15 Jun 1999 12:02:50 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id PAA12636; Tue, 15 Jun 1999 15:02:39 -0400 (EDT) Message-Id: <3.0.5.32.19990615150142.0119bc30@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 15 Jun 1999 15:01:42 -0400 To: Rich Burroughs , freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: signal 6 In-Reply-To: References: <4.1.19990614225834.0646a880@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:16 AM 6/15/99 -0700, Rich Burroughs wrote: >On Mon, 14 Jun 1999, Mike Tancsa wrote: > >> Were you playing around with your limits by chance ? > >No :) > >> Assuming you are >> running csh, what does >> limit >> give you ? > >I use bash, actually, but I hopped into csh and got this: > > cputime unlimited > filesize unlimited > datasize 524288 kbytes > stacksize 65536 kbytes > coredumpsize unlimited > memoryuse unlimited > memorylocked unlimited > maxproc 531 > openfiles 1064 > >I find it hard to believe that this is hardware, as I didn't have the >problem with 2.2, AFAIK. The only things that changed with the upgrade >were a new hard drive and a newer SCSI controller (Adaptec 2940 Ultra2). > >My first instinct was to make buildworld and installworld with the latest >sources, but, like I said, I don't seem to be able to get anything to >compile. I can't even do a kernel compile without getting signal 6... They all look reasonable... Just for fun, try and compile things using csh. I zeroed in on the limits issue, because one of our shell users had this problem with pine and bash, and it was a memory / limits issue as pine was going bonkers trying to decode a large mime attachment, and would die with a signal 6. Doubt thats the issue, but you might as well try because it could be some bizzare thing with bash... ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message