From owner-freebsd-bugs Fri May 11 3: 0: 9 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3994E37B422 for ; Fri, 11 May 2001 03:00:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f4BA04e58833; Fri, 11 May 2001 03:00:04 -0700 (PDT) (envelope-from gnats) Date: Fri, 11 May 2001 03:00:04 -0700 (PDT) Message-Id: <200105111000.f4BA04e58833@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: kern/27262: process won't be terminated after CPUTIME exceeded Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/27262; it has been noted by GNATS. From: Bruce Evans To: in@amalea.org Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/27262: process won't be terminated after CPUTIME exceeded Date: Fri, 11 May 2001 19:55:22 +1000 (EST) On Fri, 11 May 2001 in@amalea.org wrote: > >Description: > > process which exceeds CPUTIME limit by setrlimit() > will not receive signal SIGXCPU and terminate. This is intentional. -current is a work in progress: RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v Working file: kern_synch.c head: 1.134 ... ---------------------------- revision 1.120 date: 2001/01/20 02:57:59; author: jhb; state: Exp; lines: +6 -1 Temporarily disable the printf() for micruptime() going backwards, the SIGXCPU signal, and killing of processes that exceed their allowed run time until they can play nice with sched_lock. Right now they are just potentital panics waiting to happen. The printf() has bitten several people. ---------------------------- Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message