nohup(1) [hpux man page]
nohup(1) General Commands Manual nohup(1) NAME
nohup - run a command immune to hangups SYNOPSIS
command [arguments] DESCRIPTION
executes command with hangups and quits ignored. If output is not redirected by the user, both standard output and standard error are sent to If is not writable in the current directory, output is redirected to otherwise, fails. If a file is created, the file's permission bits will be set to If output from is redirected to a terminal, or is not redirected at all, the output is sent to EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty vari- able. If is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to "C". See environ(5). International Code Set Support Single- and multi-byte character code sets are supported. EXAMPLES
It is frequently desirable to apply to pipelines or lists of commands. This can be done only by placing pipelines and command lists in a single file, called a shell script. To run the script using features apply to the entire contents of file. If the shell script file is to be executed often, the need to type can be eliminated by setting execute permission on file. The script can also be run in the background with interrupts ignored (see sh(1)): file typically contains normal keyboard command sequences that one would want to continue running in case the terminal disconnects, such as: WARNINGS
Be careful to place punctuation properly. For example, in the command form: applies only to command1. To correct the problem, use the command form: Be careful of where standard error is redirected. The following command may put error messages on tape, making it unreadable: whereas puts the error messages into file EXIT STATUS
The following exit values are returned: The command specified by command was found but could not be invoked An error occurred in the nohup utility or the specified command could not be found Otherwise, the exit status of nohup will be that of the command specified. SEE ALSO
chmod(1), nice(1), sh(1), signal(5). STANDARDS CONFORMANCE
nohup(1)
Check Out this Related Man Page
nice(1) General Commands Manual nice(1) NAME
nice - run a command at nondefault priority SYNOPSIS
command [command_args] command [command_args] DESCRIPTION
The command executes command at a nondefault CPU scheduling priority. (The name is derived from being "nice" to other system users by run- ning large programs at lower priority.) Arguments The command-line arguments are as follows: priority_change The difference between the system nice value (relative priority) of the current (or parent) process and the actual system nice value at which command is to run. An unsigned value increases the system nice value for command, causing it to run at lower priority. A negative value requires superuser privileges, and assigns a lower system nice value (higher priority) to command. If the current process is not privileged, the value is silently treated as if it were 0. If the value of priority_change would result in a system nice value outside the range 0 through 39, the correspond- ing limit value of 0 or 39 is used instead. Note that a positive priority_change (lower priority) has a single option character before the numeric value; a neg- ative (higher priority) priority_change has two: the option character followed by the minus sign If is not speci- fied, it defaults to command A program, HP-UX command, user shell script, etc. to be executed at the nondefault priority. command can be run as a foreground or background process. If command is run as a background process, any nice priority_change made by the shell executes all background pro- cesses via is in addition to that specified in the command line. command_args Any arguments recognized by command. Process Priorities All processes have an associated system nice value which is used to compute the instantaneous-priority of the process when it is scheduled to run. Normally, all processes inherit the system nice value of their parent process when they are spawned. The shell etc.) can create a child process with a different priority from the current shell process by spawning the child process via the command. If the prior- ity_change value is unsigned (positive), the child process is nicer (lower in priority) relative to the parent. If the priority_change value is negative, the child process runs at a higher priority with a greater share of available system resources. To spawn a higher pri- ority child process, the parent process must be owned by a user who has the appropriate privileges. At boot-up, the system starts the process at a system nice value of 20 (system default). On most systems, all processes (down to the login shells) inherit this priority. Starting from their individual login shell processes, users can alter the system nice value of descendent processes to as much as 39, or, with appropriate privileges, as little as 0. A system nice value of 0 establishes an extremely high prior- ity, whereas a value of 39 indicates a very low priority. Ordinary users can only increase the system nice value of any child process relative to the current process; i.e., priority_change must be a positive (unsigned) value, resulting in a lower priority. To start a child process at a lower system nice value (higher priority) than the current process, the user must have the appropriate privileges, regardless of the relative nice-priority value desired. For example, using the command from a login shell whose current nice value is 20 spawns a subshell with a system nice value of 30. Attempting to use from the new shell to spawn another subshell whose system nice value would be 28, is rejected (unless the user has appropriate privileges), even though the resulting system nice value would be less than the priority of the original login shell process. The system nice value for current processes is listed under the column produced by the command (see ps(1)). Background Processes Foreground processes are run at same system nice value as the parent shell. Background processes spawned by run at the equivalent of a by default. If a background process is started via from any priority_change specified in the command is added to default Thus the command runs at a system nice value of 36 if executed from EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty vari- able. If is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to "C". See environ(5). International Code Set Support Single- and multi-byte character code sets are supported. RETURN VALUE
returns the value returned by command. EXAMPLES
The following examples assume the current process is running with a system nice value of 20 and is executed from the Korn shell (see ksh(1)). Run a program named in the current directory at the default priority_change of 10 (system nice value of 30): Run the same program in the background using a system nice value of 36 (priority_change=12 plus 4 for the Korn shell): As a user with appropriate privileges, run as a foreground process with a system nice value of 6: WARNINGS
The C shell, has a built-in command with different syntax. See csh(1) for details. SEE ALSO
csh(1), ksh(1), nohup(1), sh-posix(1), sh(1), renice(1M), nice(2). STANDARDS CONFORMANCE
nice(1)