xref: /freebsd/usr.bin/nohup/nohup.1 (revision f39bffc62c1395bde25d152c7f68fdf7cbaab414)
1.\" Copyright (c) 1989, 1990, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" This code is derived from software contributed to Berkeley by
5.\" the Institute of Electrical and Electronics Engineers, Inc.
6.\"
7.\" Redistribution and use in source and binary forms, with or without
8.\" modification, are permitted provided that the following conditions
9.\" are met:
10.\" 1. Redistributions of source code must retain the above copyright
11.\"    notice, this list of conditions and the following disclaimer.
12.\" 2. Redistributions in binary form must reproduce the above copyright
13.\"    notice, this list of conditions and the following disclaimer in the
14.\"    documentation and/or other materials provided with the distribution.
15.\" 3. Neither the name of the University nor the names of its contributors
16.\"    may be used to endorse or promote products derived from this software
17.\"    without specific prior written permission.
18.\"
19.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
29.\" SUCH DAMAGE.
30.\"
31.\"	@(#)nohup.1	8.1 (Berkeley) 6/6/93
32.\" $FreeBSD$
33.\"
34.Dd July 19, 2001
35.Dt NOHUP 1
36.Os
37.Sh NAME
38.Nm nohup
39.Nd invoke a utility immune to hangups
40.Sh SYNOPSIS
41.Nm
42.Op Fl Fl
43.Ar utility
44.Op Ar arguments
45.Sh DESCRIPTION
46The
47.Nm
48utility invokes
49.Ar utility
50with its
51.Ar arguments
52and at this time sets the signal
53.Dv SIGHUP
54to be ignored.
55If the standard output is a terminal, the standard output is
56appended to the file
57.Pa nohup.out
58in the current directory.
59If standard error is a terminal, it is directed to the same place
60as the standard output.
61.Pp
62Some shells may provide a builtin
63.Nm
64command which is similar or identical to this utility.
65Consult the
66.Xr builtin 1
67manual page.
68.Sh ENVIRONMENT
69The following variables are utilized by
70.Nm :
71.Bl -tag -width flag
72.It Ev HOME
73If the output file
74.Pa nohup.out
75cannot be created in the current directory, the
76.Nm
77utility uses the directory named by
78.Ev HOME
79to create the file.
80.It Ev PATH
81Used to locate the requested
82.Ar utility
83if the name contains no
84.Ql /
85characters.
86.El
87.Sh EXIT STATUS
88The
89.Nm
90utility exits with one of the following values:
91.Bl -tag -width Ds
92.It 126
93The
94.Ar utility
95was found, but could not be invoked.
96.It 127
97The
98.Ar utility
99could not be found or an error occurred in
100.Nm .
101.El
102.Pp
103Otherwise, the exit status of
104.Nm
105will be that of
106.Ar utility .
107.Sh SEE ALSO
108.Xr builtin 1 ,
109.Xr csh 1 ,
110.Xr signal 3
111.Sh STANDARDS
112The
113.Nm
114utility is expected to be
115.St -p1003.2
116compatible.
117.Sh BUGS
118Two or more instances of
119.Nm
120can append to the same file, which makes for a confusing output.
121