Mike Cheponis writes:
> Hi, I'm running a K6-2/400 256MB ECC 45G ATA disk with 1.5.  I had 3 ssh
> sessions into the machine (coming from a windows box, if it matters).  One
> was running "top -S -s 1" at priority -20.  Another was running "ntop" at
> priority -11.  The third ssh session was idle at the command prompt, priority 0.

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. :(

-Andrew