Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ nohup(1) — A/UX 2.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

chmod(1)

csh(1)

ksh(1)

nice(1)

sh(1)

nice(2)

nal(3)




nohup(1) nohup(1)
NAME nohup - run a command immune to hangups SYNOPSIS nohup command [arguments] DESCRIPTION nohup executes command immune to terminate (EOT, CONTROL-D) signal from the controlling terminal. Note: nohup only operates in csh(1) and sh(1)). With nohup, the priority is automatically incremented by 5. nohup should be used with processes running in background (with &) in order to prevent them from responding to inter- rupts or stealing the input from the next person who logs in on the same terminal. In csh, processes run in the back- ground are automatically immune to hangups. If output is not redirected by the user, both the standard output and standard error are sent to a file named nohup.out. If nohup.out is not writable in the current directory, output is redirected to $HOME/nohup.out. EXAMPLES nohup nroff -mm docsfile | lp runs the nroff command shown, immune to hangups, quits, and interrupts. It is frequently desirable to apply nohup to pipelines or lists of commands. This can be done only by placing pipe- lines and commands lists in a single file, called a shell procedure. One can then issue: nohup sh file and the nohup applies to everything in file. If the shell procedure file is to be executed often, then the need to type sh can be eliminated by giving file execute permission. Add an ampersand and the contents of file are run in the background with interrupts also ignored (see sh(1) and ksh(1)): nohup file & An example of what the contents of file could be is: tbl ofile | eqn | nroff > nfile April, 1990 1



nohup(1) nohup(1)
FILES /bin/nohup nohup.out standard output and standard error file. SEE ALSO chmod(1), csh(1), ksh(1), nice(1), sh(1), nice(2), sig- nal(3). WARNINGS nohup command1; command2 nohup applies only to command1 nohup (command1; command2) is syntactically incorrect. Be careful of where standard error is directed. The follow- ing command may put error messages on disk, making it un- readable: nohup cpio -o < list > /dev/dsk/c8d0s0 2>&1 & while the next command: nohup cpio -o < list > /dev/dsk/c8d0s0 2>errors & puts the error messages into the file errors. 2 April, 1990

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026