mirror of
https://github.com/openvswitch/ovs
synced 2025-10-11 13:57:52 +00:00
fda546bd0b
The following code does not add any users yet. The visioned workflow that this piece of code should work with is: * Create a windows service through a startup script with a tool like 'sc' ex: sc create ovsdb-server binpath= "C:\openvswitch\usr\sbin\ovsdb-server.exe -vconsole:off -vsyslog:off -vfile:info --remote=ptcp:6632:127.0.0.1 --log-file --service-monitor --service" * Start the service from the startup script. ex: sc start ovsdb-server * Terminate the service during shutdown process. ex: sc stop ovsdb-server * Abrupt termination will restart the service. Signed-off-by: Gurucharan Shetty <gshetty@nicira.com> Acked-by: Ben Pfaff <blp@nicira.com>
53 lines
2.0 KiB
Groff
53 lines
2.0 KiB
Groff
The following options are valid on POSIX based platforms.
|
|
.TP
|
|
\fB\-\-pidfile\fR[\fB=\fIpidfile\fR]
|
|
Causes a file (by default, \fB\*(PN.pid\fR) to be created indicating
|
|
the PID of the running process. If the \fIpidfile\fR argument is not
|
|
specified, or
|
|
if it does not begin with \fB/\fR, then it is created in
|
|
\fB@RUNDIR@\fR.
|
|
.IP
|
|
If \fB\-\-pidfile\fR is not specified, no pidfile is created.
|
|
.
|
|
.TP
|
|
\fB\-\-overwrite\-pidfile\fR
|
|
By default, when \fB\-\-pidfile\fR is specified and the specified pidfile
|
|
already exists and is locked by a running process, \fB\*(PN\fR refuses
|
|
to start. Specify \fB\-\-overwrite\-pidfile\fR to cause it to instead
|
|
overwrite the pidfile.
|
|
.IP
|
|
When \fB\-\-pidfile\fR is not specified, this option has no effect.
|
|
.
|
|
.TP
|
|
\fB\-\-detach\fR
|
|
Causes \fB\*(PN\fR to detach itself from the foreground session and
|
|
run as a background process. \*(DD
|
|
.
|
|
.TP
|
|
\fB\-\-monitor\fR
|
|
Creates an additional process to monitor the \fB\*(PN\fR daemon. If
|
|
the daemon dies due to a signal that indicates a programming error
|
|
(\fBSIGABRT\fR, \fBSIGALRM\fR, \fBSIGBUS\fR, \fBSIGFPE\fR,
|
|
\fBSIGILL\fR, \fBSIGPIPE\fR, \fBSIGSEGV\fR, \fBSIGXCPU\fR, or
|
|
\fBSIGXFSZ\fR) then the monitor process starts a new copy of it. If
|
|
the daemon dies or exits for another reason, the monitor process exits.
|
|
.IP
|
|
This option is normally used with \fB\-\-detach\fR, but it also
|
|
functions without it.
|
|
.
|
|
.TP
|
|
\fB\-\-no\-chdir\fR
|
|
By default, when \fB\-\-detach\fR is specified, \fB\*(PN\fR
|
|
changes its current working directory to the root directory after it
|
|
detaches. Otherwise, invoking \fB\*(PN\fR from a carelessly chosen
|
|
directory would prevent the administrator from unmounting the file
|
|
system that holds that directory.
|
|
.IP
|
|
Specifying \fB\-\-no\-chdir\fR suppresses this behavior, preventing
|
|
\fB\*(PN\fR from changing its current working directory. This may be
|
|
useful for collecting core files, since it is common behavior to write
|
|
core dumps into the current working directory and the root directory
|
|
is not a good directory to use.
|
|
.IP
|
|
This option has no effect when \fB\-\-detach\fR is not specified.
|