Mac Developer Library Developer


This manual page is for Mac OS X version 10.9

If you are running a different version of Mac OS X, view the documentation locally:

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

NOHUP(1)                  BSD General Commands Manual                 NOHUP(1)

     nohup -- invoke a utility immune to hangups

     nohup [--] utility [arguments]

     The nohup utility invokes utility with its arguments and at this time sets the signal SIGHUP to be
     ignored.  If the standard output is a terminal, the standard output is appended to the file nohup.out
     in the current directory.  If standard error is a terminal, it is directed to the same place as the
     standard output.

     Some shells may provide a builtin nohup command which is similar or identical to this utility.  Consult
     the builtin(1) manual page.

     The following variables are utilized by nohup:

     HOME  If the output file nohup.out cannot be created in the current directory, the nohup utility uses
           the directory named by HOME to create the file.

     PATH  Used to locate the requested utility if the name contains no `/' characters.

     The nohup utility exits with one of the following values:

     126     The utility was found, but could not be invoked.

     127     The utility could not be found or an error occurred in nohup.

     Otherwise, the exit status of nohup will be that of utility.

     builtin(1), csh(1), signal(3)

     The nohup utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.

     Two or more instances of nohup can append to the same file, which makes for a confusing output.

BSD                              July 19, 2001                             BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.