Re: changing the text of info text of nice

[Pádraig Brady]

On 11/22/2012 12:30 PM, Karl-Philipp Richter wrote:
> There should be a differentiation between the setting of niceness at start and after 
> start of a command. If you read the info text without knowing about renice you might 
> think that nice is able to "modify" the niceness after start. There should be 
> clear statement that it can't and a link to the renice command.

Good point. It's a bit ambiguous.
How about...


diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 70e7ca0..4a4d72a 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -15676,8 +15676,9 @@ the exit status of @var{command} otherwise
 @cindex scheduling, affecting
 @cindex appropriate privileges

-@command{nice} prints or modifies a process's @dfn{niceness},
-a parameter that affects whether the process is scheduled favorably.
+@command{nice} prints a process's @dfn{niceness}, or runs
+a command with modified niceness.  @dfn{niceness} affects how
+favorably the process is scheduled in the system.
 Synopsis:

 @example
@@ -15712,6 +15713,9 @@ built-in utilities}).

 @mayConflictWithShellBuiltIn{nice}

+Note to change the @dfn{niceness} of an existing process,
+one needs to use the @command{renice} command.
+
 The program accepts the following option.  Also see @ref{Common options}.
 Options must precede operands.

diff --git a/man/nice.x b/man/nice.x
index 3448d69..952cb10 100644
--- a/man/nice.x
+++ b/man/nice.x
@@ -3,4 +3,4 @@ nice \- run a program with modified scheduling priority
 [DESCRIPTION]
 .\" Add any additional description here
 [SEE ALSO]
-nice(2)
+nice(2), renice(1)