Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA13051; Fri, 15 Mar 96 11:43:36 EST
Received: from liquor.cabi.net by MIT.EDU with SMTP
	id AA24160; Fri, 15 Mar 96 11:42:47 EST
Received: by liquor.cabi.net (8.7.3/8.7.3) id LAA12971; Fri, 15 Mar 1996 11:41:12 -0500
Resent-Date: Fri, 15 Mar 1996 11:41:12 -0500
Date: Fri, 15 Mar 1996 16:36:36 GMT
From: Sergej Melnik <k961909@dcs.kingston.ac.uk>
Message-Id: <199603151636.QAA03591@vulture.dcs.king.ac.uk>
To: lstein@kaa.crbm.cnrs-mop.fr
Cc: java-linux@java.blackdown.org, mieg@kaa.crbm.cnrs-mop.fr
In-Reply-To: <199603151437.PAA06152@pico.crbm.cnrs-mop.fr> (message from Lincoln Stein on Fri, 15 Mar 1996 15:37:40 +0100)
Subject: Re: Thread.yield() doesn't
Resent-Message-Id: <"TFiYy2.0.f93.orPIn"@liquor>
Resent-From: java-linux@java.blackdown.org
X-Mailing-List: <java-linux@java.blackdown.org> archive/latest/1403
X-Loop: java-linux@java.blackdown.org
Precedence: list
Resent-Sender: java-linux-request@java.blackdown.org


> The problem is that time-slicing doesn't seem to be implemented on the
> Linux platform.  The first thread grabs the CPU and holds onto it
> until its inner read-and-parse loop is done.  Very annoying.

Try to set the thread's priority to Thread.MAX_PRIORITY.
Concerning similar question you may want to see Russ Ethington's (many thanks for him)
programming tutorials (http://users.aol.com/thingtone/workshop/tutorial.htm).

Regards,

Sergej.

