*BSD News Article 58638


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!col.hp.com!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!in2.uu.net!news.tek.com!news.cna.tek.com!not-for-mail
From: frankm@solaris.cna.tek.com (Frank 'Scruffy' Miller)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: SEGV's with 2.0.1
Date: 31 Dec 1995 17:12:41 -0800
Organization: Tektronix, Inc., Redmond, OR, USA
Lines: 41
Message-ID: <4c7ce9$mbb@solaris.cna.tek.com>
NNTP-Posting-Host: solaris.cna.tek.com

I've brought up innd1.4 unoff for a friend on a BSDI box.  I must
admit a bit of unfamiliarity with this flavor ... my BSD experience stems
from SunOS (and am now a Solaris 2.x guy).  He's got 2.0.1 ...

I get many random SEGV's with not only innd (and associated apps), but
I've seen cores from fsck, gzip, sh ..

There are no compaints in messages from the OS ... 

I've tuned the OS as so:

# News tuning options
options               DFLDSIZ=67108864        # 64 meg default (def 16)
options               MAXDSIZ=134217728       # 128 meg max data (def 64)
options               CHILD_MAX=256           # 256 (def 64)                 

Also, rc.news tweaks the following:

# Get around default 16Mb data size limit in BSDI.
unlimit datasize
limit openfiles 256                  

Stack traces from innd, for example, are all at different functions
when the SEGV transpired.

If it was hardware, seems that I'd get panic's with kernel memory.  Then
again, the kernel image is always resident and not paged.  But, I'm
not finding core dumps from root daemons (syslogd, inetd, etc).

Clues?

Thanks!

Frank

PS.  Please send e-mail if possible as I'm too busy for a week to read 
news.
-- 
 Frank 'Scruff' Miller		| Internet: Frank.Miller@master.cna.tek.com 
 Software Engineer/UNIX Systems | "I went into her cave and returned without
 Tektronix CNA Division         |  the ears of a rabbit."