Brian Dessent wrote:
Yitzchak Scott-Thoennes wrote:
On Fri, Jun 11, 2004 at 05:42:38AM -0700, Brian Dessent wrote:
reserved for real-time processes. The remaining range 1-15 are the
regular (dynamic) priorities that most processes run with. In reality
you don't set the priority directly this way,
Yitzchak Scott-Thoennes wrote:
>
> On Fri, Jun 11, 2004 at 05:42:38AM -0700, Brian Dessent wrote:
> > reserved for real-time processes. The remaining range 1-15 are the
> > regular (dynamic) priorities that most processes run with. In reality
> > you don't set the priority directly this way, rat
On Fri, Jun 11, 2004 at 05:42:38AM -0700, Brian Dessent wrote:
> reserved for real-time processes. The remaining range 1-15 are the
> regular (dynamic) priorities that most processes run with. In reality
> you don't set the priority directly this way, rather you choose a
> priority class (realtim
"Mironov, Leonid {PBG}" wrote:
> If I am to believe windows task manager windows processes can have 6
> priority levels - realtime, high, above normal, normal, below normal and
> low, but cygwin nice can set only 2: when -n parameter is above 0 priority
> is set to low, when -n is below 0 priority
Mironov, Leonid {PBG} wrote:
If I am to believe windows task manager windows processes can have 6
priority levels - realtime, high, above normal, normal, below normal and
low, but cygwin nice can set only 2: when -n parameter is above 0 priority
is set to low, when -n is below 0 priority is set to
If I am to believe windows task manager windows processes can have 6
priority levels - realtime, high, above normal, normal, below normal and
low, but cygwin nice can set only 2: when -n parameter is above 0 priority
is set to low, when -n is below 0 priority is set to high, actual value of
-n para
6 matches
Mail list logo
