nohup(1)                                                 nohup(1)



     NAME
          nohup - run a command immune to hangups (ksh and sh only)

     SYNOPSIS
          nohup command [arguments]

     DESCRIPTION
          nohup executes command immune to terminate (EOT, CONTROL-d)
          signal from the controlling terminal.  With nohup, the
          priority is automatically incremented by 5.  nohup should be
          used with processes running in background (with &) in order
          to prevent it from responding to interrupts or stealing the
          input from the next person who logs in on the same terminal.
          In csh, processes run in background are automatically immune
          to hangups.

          If output is not redirected by the user, both the standard
          output and standard error are sent to nohup.out.  If
          nohup.out is not writable in the current directory, output
          is redirected to $HOMEnohup.out.

     EXAMPLE
               nohup  nroff -ms  docsfile | lpr

          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
          pipelines 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

     FILES
          /bin/nohup
          nohup.out   standard output and standard error file.

     SEE ALSO



     Page 1                                        (last mod. 1/16/87)

     nohup(1)                                                 nohup(1)



          chmod(1), csh(1), ksh(1), nice(1), sh(1), nice(2),
          signal(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
          following command may put error messages on tape, making it
          unreadable:

               nohup cpio -o <list >/dev/rmt/1m&

               while the next command:


               nohup cpio -o <list >/dev/rmt/1m 2>errors&

          puts the error messages into the file errors.

































     Page 2                                        (last mod. 1/16/87)