Date: Fri, 11 May 2001 03:00:04 -0700 (PDT) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/27262: process won't be terminated after CPUTIME exceeded Message-ID: <200105111000.f4BA04e58833@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/27262; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105111000.f4BA04e58833>