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 Creates an additional process to monitor the \fB\*(PN\fR daemon. If
25 the daemon dies due to a signal that indicates a programming error
26 (e.g. \fBSIGSEGV\fR, \fBSIGABRT\fR), then the monitor process starts a
27 new copy of it. If the daemon die or exits for another reason, the
28 monitor process exits.
30 This option is normally used with \fB--detach\fR, but it also
35 By default, when \fB--detach\fR is specified, \fB\*(PN\fR
36 changes its current working directory to the root directory after it
37 detaches. Otherwise, invoking \fB\*(PN\fR from a carelessly chosen
38 directory would prevent the administrator from unmounting the file
39 system that holds that directory.
41 Specifying \fB--no-chdir\fR suppresses this behavior, preventing
42 \fB\*(PN\fR from changing its current working directory. This may be
43 useful for collecting core files, since it is common behavior to write
44 core dumps into the current working directory and the root directory
45 is not a good directory to use.
47 This option has no effect when \fB--detach\fR is not specified.