Date: Sat, 14 Mar 1998 03:00:40 +0100 (CET) From: Mikael Karpberg <karpen@ocean.campus.luth.se> To: dnelson@emsphone.com (Dan Nelson) Cc: freebsd-current@FreeBSD.ORG Subject: Re: idprio/rtprio Message-ID: <199803140200.DAA21272@ocean.campus.luth.se> In-Reply-To: <19980312123427.A12954@emsphone.com> from Dan Nelson at "Mar 12, 98 12:34:27 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Dan Nelson: > In the last episode (Mar 12), Mikael Karpberg said: > > > It's the man page that's wrong since this was disallowed awhile > > > back after BEST Internet filed a PR noting that an ordinary user > > > could put your system in very bad shape by using it. The man page > > > has been fixed, thanks. > > > > Hmm... I just can't seem to remember how. Breif summary? > > > > How? Easy. Run rc564 at idlepri, and run another high-CPU process. > Eventually, the rc564 process will try a filesystem operation. After > that, every process trying to hit a file will hang too. If you > unidprio the rc564 process or kill the high-cpu process (letting rc564 > run again) everything will return to normal. I've done this to myself > three or four times, and have resorted to running rc564 at nice 20 for > now. Ah, I see. But... shouldn't that be handled by some priority inheritance thingie in the scheduler, instead? I mean, it's no better if root runs it, is it? So it renders idleprio basically useless, no? Or is this one of those "YES! Exactly right. Where's your patches?" cases? /Mikael 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?199803140200.DAA21272>