Used B<> instead of C<> when highlighting options and parameters in
POD documentation. Not only do they look nicer emboldened, but it's also what's suggested in perlpod.
This commit is contained in:
parent
112da861ca
commit
fd671cec3d
16 changed files with 179 additions and 179 deletions
|
|
@ -151,32 +151,32 @@ S.P.E.C.T.R.E. is the Supervisor of Perplexing Event-handling
|
|||
Contraptions for Triggering Relentless Executions. It triggers
|
||||
WebGUI's workflow and scheduling functions.
|
||||
|
||||
Spectre's configuration file, C<spectre.conf>, is located under
|
||||
Spectre's configuration file, B<spectre.conf>, is located under
|
||||
the WebGUI filesystem hierarchy.
|
||||
|
||||
=over
|
||||
|
||||
=item C<--daemon>
|
||||
=item B<--daemon>
|
||||
|
||||
Starts the Spectre server forking as a background daemon. This
|
||||
can be done by hand, but it is usually handled by a startup
|
||||
script.
|
||||
|
||||
=item C<--run>
|
||||
=item B<--run>
|
||||
|
||||
Starts Spectre in the foreground without forking as a daemon.
|
||||
|
||||
=item C<--debug>
|
||||
=item B<--debug>
|
||||
|
||||
If this option is specified at startup either in C<--daemon>
|
||||
or C<--run> mode, Spectre will provide verbose debug to standard
|
||||
If this option is specified at startup either in B<--daemon>
|
||||
or B<--run> mode, Spectre will provide verbose debug to standard
|
||||
output so that you can see exactly what it's doing.
|
||||
|
||||
=item C<--shutdown>
|
||||
=item B<--shutdown>
|
||||
|
||||
Stops the running Spectre server.
|
||||
|
||||
=item C<--ping>
|
||||
=item B<--ping>
|
||||
|
||||
Pings Spectre to see if it is alive. If Spectre is alive, you'll get
|
||||
confirmation with a message like
|
||||
|
|
@ -188,16 +188,16 @@ If Spectre doesn't seem to be alive, you'll get a message like
|
|||
Spectre is not responding.
|
||||
Unable to connect to <IP-address>:<Port>
|
||||
|
||||
where C<IP-address> is the IP address and C<Port> is the port number
|
||||
where B<IP-address> is the IP address and B<Port> is the port number
|
||||
where Spectre should be listening for connections on according to
|
||||
C<spectre.conf>.
|
||||
B<spectre.conf>.
|
||||
|
||||
=item C<--status>
|
||||
=item B<--status>
|
||||
|
||||
Shows a summary of Spectre's internal status. The summary contains
|
||||
a tally of suspended, waiting and running WebGUI Workflows.
|
||||
|
||||
=item C<--test>
|
||||
=item B<--test>
|
||||
|
||||
Tests whether Spectre can connect to WebGUI. Both Spectre
|
||||
and the Apache server running WebGUI must be running for this
|
||||
|
|
@ -205,7 +205,7 @@ option to work. It will test the connection between every site
|
|||
and Spectre, by looking for configuration files in WebGUI's
|
||||
configuration directory, showing success or failure in each case.
|
||||
|
||||
=item C<--help>
|
||||
=item B<--help>
|
||||
|
||||
Shows this documentation, then exits.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue