From owner-freebsd-current Wed May 13 23:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15929 for freebsd-current-outgoing; Wed, 13 May 1998 23:11:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15920 for ; Wed, 13 May 1998 23:10:56 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from unicorn.carrier.kiev.ua (unicorn.carrier.kiev.ua [193.193.193.113]) by burka.carrier.kiev.ua (8.8.8/8.Who.Cares) with ESMTP id JAA21983 for ; Thu, 14 May 1998 09:10:32 +0300 (EEST) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by unicorn.carrier.kiev.ua (8.8.8/8.8.7) with ESMTP id JAA05087; Thu, 14 May 1998 09:10:30 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id JAA20442; Thu, 14 May 1998 09:01:27 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id IAA15091; Thu, 14 May 1998 08:47:15 +0300 (EEST) (envelope-from archer) Message-ID: <19980514084714.18350@carrier.kiev.ua> Date: Thu, 14 May 1998 08:47:14 +0300 From: Alexander Litvin To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: daemons exiting on signal 11 References: <19980513093110.21002@carrier.kiev.ua> <199805140302.UAA04302@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199805140302.UAA04302@usr08.primenet.com>; from Terry Lambert on Thu, May 14, 1998 at 03:02:08AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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