Date: Tue, 18 Aug 1998 21:05:03 +0000 From: Mike Smith <mike@smith.net.au> To: current@FreeBSD.ORG Subject: Unwanted sig24 problems? Message-ID: <199808182105.VAA03757@dingo.cdrom.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808182105.VAA03757>