Date: Fri, 24 May 2002 08:04:44 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: freebsd-hackers@FreeBSD.ORG Cc: dufault@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_fork.c Message-ID: <20020524080444.R8148@gsmx07.alcatel.com.au> In-Reply-To: <200202190315.g1J3FSV14877@freefall.freebsd.org>; from silby@FreeBSD.ORG on Mon, Feb 18, 2002 at 07:15:28PM -0800 References: <200202190315.g1J3FSV14877@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[The reference is ancient but I think it's still relevant.] On Mon, Feb 18, 2002 at 07:15:28PM -0800, Mike Silbersack wrote: >silby 2002/02/18 19:15:28 PST > > Modified files: > sys/kern kern_fork.c > Log: > A few misc forkbomb defenses: ... > - Remove the printing of "proc: table full". When the table > really is full, this would flood the screen/logs, making > the problem tougher to deal with. I've bumped into a similar problem when running StarOffice on a system without _KPOSIX_PRIORITY_SCHEDULING. It seems that StarOffice likes calling sched_yield() and doesn't take ENOSYS as a hint. My syslog entries showed repeat counts in the high 5-figure region. It's useful to know that a process wants to use the RT scheduling functions, but it would be nice if this message could be rate-limited so that processes that ignore return codes won't flood the console. I'm not sure how to achieve this - since doing it properly implies additional per-process state - and I don't think it's important enough to bloat struct proc. [I don't have the RT extensions enabled because there was a past thread about them being susceptable to priority inversion deadlocks - is this still true]. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020524080444.R8148>