public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: ready for 2.3?
Date: Sat, 28 Sep 2002 04:51:00 -0000	[thread overview]
Message-ID: <20020928135106.A10322@suse.de> (raw)
In-Reply-To: <3D955075.4060405@redhat.com>; from drepper@redhat.com on Fri, Sep 27, 2002 at 11:47:17PM -0700


Hi Uli,

there is one patch for the nice() emulation from me, where I and
Andreas Jaeger already asked you for inclusion in the official tree,
but never got an answer. Since all Linux Distributions have this
patch in their glibc version, I think we should include it in the
official release.

The problem is, that, if the result of the current priority of a
process and the added nice value is out of the priority range, nice
should return the new priority which is really used, and not our
calculated value:

2002-03-02  Thorsten Kukuk  <kukuk@suse.de>

        * sysdeps/unix/nice.c: Use getpriority() for the return value

--- sysdeps/unix/nice.c
+++ sysdeps/unix/nice.c 2002/03/02 09:40:14
@@ -43,7 +43,7 @@
 
   result = setpriority (PRIO_PROCESS, 0, prio + incr);
   if (result != -1)
-    return prio + incr;
+    return getpriority (PRIO_PROCESS, 0);
   else
     return -1;

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE Linux AG        Deutschherrnstr. 15-19        D-90429 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

  reply	other threads:[~2002-09-28 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 23:47 Ulrich Drepper
2002-09-28  4:51 ` Thorsten Kukuk [this message]
2002-09-28 12:14   ` Ulrich Drepper
2002-09-28 15:02 ` Roland McGrath
2002-09-28 15:34   ` Ulrich Drepper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020928135106.A10322@suse.de \
    --to=kukuk@suse.de \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).