Date: Thu, 14 May 1998 22:18:25 +0930 From: Matthew Thyer <thyerm@camtech.net.au> To: Alexander Litvin <archer@lucky.net> Cc: Terry Lambert <tlambert@primenet.com>, current@FreeBSD.ORG Subject: Re: daemons exiting on signal 11 Message-ID: <355AE819.5F715139@camtech.net.au> References: <19980513093110.21002@carrier.kiev.ua> <199805140302.UAA04302@usr08.primenet.com> <19980514084714.18350@carrier.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
NetscapeŽ Communicator 4.05 (export version from the port Fortified to US encryption) crashed with a sig 10 on me the first time I ran it after a full rebuild at ctm-src-cur.3366 (which includes all the VM fixes). I also am running the latest softupdates on my 3GB /usr (the only fs other than /). Since then its been solid as a rock and even exits quickly every time. I haven't seen it hanging around forever using up all the CPU time like it used to do a lot of the time when you quit from it. I still have the core, what debuging info do you want ? Alexander Litvin wrote: > > On Thu, May 14, 1998 at 03:02:08AM +0000, Terry Lambert 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 :-\ > > > > For readers who might have been alarmed by this: > > > > Note that this is not indicative of a problem in the soft updates > > code. This means that he was out of swap + RAM, and when cron > > went to get a page, it was denied, and could not continue to run. > > Well, I'm not blaming softupdates in this case. But still, problem > exists. > > May be I was not clear: cron _didn't_ exit with SIGSEGV, it continued > to run. But it was unable to fork to run cron jobs. I noticed that > after some 10 hours (I'm on dialup, and I just saw no attempts of > my machine to dial to get mail). > > Note: 'make buildworld' had already been finished for some 4 hours, > but cron still was in that strange state: running, but all attempts > to fork to run some jobs failed: > > May 13 08:50:00 grape /kernel: pid 22955 (cron), uid 0: exited on signal 11 > May 13 08:55:00 grape /kernel: pid 22969 (cron), uid 0: exited on signal 11 > May 13 08:55:00 grape /kernel: pid 22970 (cron), uid 0: exited on signal 11 > > The same was with sendmail (in fact because of this my original letter, > which I had written in the morning, remained in queue till evening). > > I can imagine what happenes. And I'm not absolutely shure that it is an > error, just would like to hear some authoritative opinion ;) > > > > > > > Terry Lambert > > terry@lambert.org > > --- > > Any opinions in this posting are my own and not those of my present > > or previous employers. > > Alexander Litvin > > --- > Shaw's Principle: > Build a system that even a fool can use, and only a fool will > want to use it. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?355AE819.5F715139>