> How did top get to be running at '-20' anyway?  On my machine, even with
> a '-s 0' argument, top always has a priority of 40-60.  If it was running
> at -20 it would always be scheduled to run if it wanted to, and could easily
> starve any other process.  How it got that way, I have no idea. :(

Sorry, I should have said "nice at -20".  Then I'm seeing the "priority" to
be -12 or so.

I start it as "top -S -s 1".

I reniced "top" inside "top": r -20 <pid-of-top>

Yes, it -could- starve other processes, but then "top" would be broken, I 
think.

-Mike