xref: /freebsd/usr.bin/nohup/nohup.1 (revision 2008043f386721d58158e37e0d7e50df8095942d)
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.\"
33.Dd June 26, 2023
34.Dt NOHUP 1
35.Os
36.Sh NAME
37.Nm nohup
38.Nd invoke a utility immune to hangups
39.Sh SYNOPSIS
40.Nm
41.Op Fl Fl
42.Ar utility
43.Op Ar arguments
44.Sh DESCRIPTION
45The
46.Nm
47utility invokes
48.Ar utility
49with its
50.Ar arguments
51and at this time sets the signal
52.Dv SIGHUP
53to be ignored.
54If the standard output is a terminal, the standard output is
55appended to the file
56.Pa nohup.out
57in the current directory.
58If standard error is a terminal, it is directed to the same place
59as the standard output.
60.Pp
61Some shells may provide a builtin
62.Nm
63command which is similar or identical to this utility.
64Consult the
65.Xr builtin 1
66manual page.
67.Sh ENVIRONMENT
68The following variables are utilized by
69.Nm :
70.Bl -tag -width flag
71.It Ev HOME
72If the output file
73.Pa nohup.out
74cannot be created in the current directory, the
75.Nm
76utility uses the directory named by
77.Ev HOME
78to create the file.
79.It Ev PATH
80Used to locate the requested
81.Ar utility
82if the name contains no
83.Ql /
84characters.
85.El
86.Sh EXIT STATUS
87The
88.Nm
89utility exits with one of the following values:
90.Bl -tag -width Ds
91.It 126
92The
93.Ar utility
94was found, but could not be invoked.
95.It 127
96The
97.Ar utility
98could not be found or an error occurred in
99.Nm .
100.El
101.Pp
102Otherwise, the exit status of
103.Nm
104will be that of
105.Ar utility .
106.Sh SEE ALSO
107.Xr builtin 1 ,
108.Xr csh 1 ,
109.Xr timeout 1 ,
110.Xr signal 3 ,
111.Xr daemon 8
112.Sh STANDARDS
113The
114.Nm
115utility is expected to be
116.St -p1003.2
117compatible.
118.Sh BUGS
119Two or more instances of
120.Nm
121can append to the same file, which makes for a confusing output.
122