From owner-freebsd-current Tue Aug 18 21:07:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13192 for freebsd-current-outgoing; Tue, 18 Aug 1998 21:07:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com ([203.8.14.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13185 for ; Tue, 18 Aug 1998 21:06:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.hilink.com.au [127.0.0.1] (may be forged)) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA03757 for ; Tue, 18 Aug 1998 21:05:03 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808182105.VAA03757@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Unwanted sig24 problems? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Aug 1998 21:05:03 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An odd one here; I recently reinstalled -current on my laptop, and with a kernel built this morning I am getting (important) processes killed with SIGXCPU. (eg. the X server). I start the server by hand, and I'm also seeing user processes (emacs, exmh, anything long-lived and busy) dying similarly. dingo:~>limit cputime unlimited filesize unlimited datasize 524288 kbytes stacksize 65536 kbytes coredumpsize unlimited memoryuse 32768 kbytes descriptors 1024 memorylocked unlimited maxproc 64 So I'm fairly happy this isn't a resource configuration problem. Any ideas? (Very irritating this is. 8( ) I managed to reproduce the problem quite quickly with 'top' running with a refresh delay of 0 in an xterm, unfortunately it took the shell with it at about 4 minutes. (Slightly over 4:15, unfortunately). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message