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 the \fIpidfile\fR argument is not
6 if it does not begin with \fB/\fR, then it is created in
9 If \fB\-\-pidfile\fR is not specified, no pidfile is created.
12 \fB\-\-overwrite\-pidfile\fR
13 By default, when \fB\-\-pidfile\fR is specified and the specified pidfile
14 already exists and is locked by a running process, \fB\*(PN\fR refuses
15 to start. Specify \fB\-\-overwrite\-pidfile\fR to cause it to instead
16 overwrite the pidfile.
18 When \fB\-\-pidfile\fR is not specified, this option has no effect.
22 Causes \fB\*(PN\fR to detach itself from the foreground session and
23 run as a background process. \*(DD
27 Creates an additional process to monitor the \fB\*(PN\fR daemon. If
28 the daemon dies due to a signal that indicates a programming error
29 (e.g. \fBSIGSEGV\fR, \fBSIGABRT\fR), then the monitor process starts a
30 new copy of it. If the daemon die or exits for another reason, the
31 monitor process exits.
33 This option is normally used with \fB\-\-detach\fR, but it also
38 By default, when \fB\-\-detach\fR is specified, \fB\*(PN\fR
39 changes its current working directory to the root directory after it
40 detaches. Otherwise, invoking \fB\*(PN\fR from a carelessly chosen
41 directory would prevent the administrator from unmounting the file
42 system that holds that directory.
44 Specifying \fB\-\-no\-chdir\fR suppresses this behavior, preventing
45 \fB\*(PN\fR from changing its current working directory. This may be
46 useful for collecting core files, since it is common behavior to write
47 core dumps into the current working directory and the root directory
48 is not a good directory to use.
50 This option has no effect when \fB\-\-detach\fR is not specified.