2 \fB--pidfile\fR[\fB=\fIpidfile\fR]
3 Causes a file (by default, \fB\*(PN.pid\fR) to be created indicating
4 the PID of the running process. If \fIpidfile\fR is not specified, or
5 if it does not begin with \fB/\fR, then it is created in
9 \fB--overwrite-pidfile\fR
10 By default, when \fB--pidfile\fR is specified and the specified pidfile
11 already exists and is locked by a running process, \fB\*(PN\fR refuses
12 to start. Specify \fB--overwrite-pidfile\fR to cause it to instead
13 overwrite the pidfile.
15 When \fB--pidfile\fR is not specified, this option has no effect.
19 Causes \fB\*(PN\fR to detach itself from the foreground session and
20 run as a background process.
24 By default, when \fB--detach\fR is specified, \fB\*(PN\fR
25 changes its current working directory to the root directory after it
26 detaches. Otherwise, invoking \fB\*(PN\fR from a carelessly chosen
27 directory would prevent the administrator from unmounting the file
28 system that holds that directory.
30 Specifying \fB--no-chdir\fR suppresses this behavior, preventing
31 \fB\*(PN\fR from changing its current working directory. This may be
32 useful for collecting core files, since it is common behavior to write
33 core dumps into the current working directory and the root directory
34 is not a good directory to use.
36 This option has no effect when \fB--detach\fR is not specified.