Rick Petree asks:
> 1. When you sent a process to the background how do you turn off the
> annoying error messages that may come up. For example: you use the find
> command to locate a file and you send this long process to the background
> and direct the output to a file that you will check later for the results.
The exact syntax depends on which shell you're using.
Near as I can tell, csh and its derivatives (tcsh for instance) don't
provide for sending stderr to a separate file if stdout is also being
redirected. I'm at a loss to explain this as it seems like quite a
regression in basic functionality. (Though I'm sure if I'm wrong or
if there's a stunt that allows separation of the streams then someone
will write a note within a few milliseconds of reading this one... :-) )
The Bourne shell is easier. To separate and redirect the output of your
find command you can do this:
$ find . -name foo -print >find.out 2>find.error &
The "2" is a reference to the "stderr" stream. You don't need a "1" for
stdout because that's assumed... I believe this syntax will work for
either the Korn shell or bash as well.
> 2. When using the nice command to change the priority of a process how
> does it work if the process is already running?? Do I need to stop the
> process or can it be done on-the-fly??
If you want to change the priority of a *running* process then you
should look at renice(8). You can alter processes or process groups
which you own, but you can't make their priorities < 0. Only the
root user can do that, or change the priority of arbitrary processes
in the system.
-- Farrell
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
