|
Check-in Number:
|
3449 | |
| Date: |
2003-Jun-23 16:53:10 (local)
2003-Jun-23 14:53:10 (UTC) |
| User: | ms |
| Branch: | |
| Comment: |
Use term run-command consistently throughout docs. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/rc/rc-sample.pod 1.10 -> 1.11
--- rc-sample.pod 2002/03/26 17:11:06 1.10
+++ rc-sample.pod 2003/06/23 14:53:10 1.11
@@ -34,10 +34,10 @@
This documents typical use cases for B<OSSP rc>.
-=head1 USE CASE: OpenPKG Runcommand Facility
+=head1 USE CASE: OpenPKG Run-command Facility
This describes how B<OSSP rc> is used as the B<OpenPKG>
-(http://www.openpkg.org/) runcommand facility.
+(http://www.openpkg.org/) run-command facility.
First, the involved files:
@@ -111,7 +111,7 @@
This is the B<OpenPKG> configuration script where the administrator
overrides the variables from the script's C<%config> sections. It it
generated (as an empty file) on B<OpenPKG> bootstrap time and manually
-edited later to influence the behaviours of the package's runcommand
+edited later to influence the behaviours of the package's run-command
scripts (here F</cw/etc/rc.d/rc.foo>).
foo_enable=yes
@@ -119,7 +119,7 @@
=item F</cw/etc/rc.d/rc.foo>
-This is the example runcommand script of an B<OpenPKG> package C<foo>.
+This is the example run-command script of an B<OpenPKG> package C<foo>.
It is installed by package C<foo> and used read-only.
#! /cw/etc/rc
|
|
ossp-pkg/rc/rc.pod 1.34 -> 1.35
--- rc.pod 2003/06/23 14:46:33 1.34
+++ rc.pod 2003/06/23 14:53:10 1.35
@@ -244,9 +244,9 @@
=head1 COMMAND INTERPRETER
As long as a valid interpreter path is specified in the section labels of a
-F<rcfile>, the runcommands resulting from a --eval, --exec, or --print
+F<rcfile>, the run-commands resulting from a --eval, --exec, or --print
operation can be written in any runtime-interpreted language. This means that
-a perl programmer can write runcommands in perl, and specify the perl
+a perl programmer can write run-commands in perl, and specify the perl
interpreter path in the corresponding section label of the F<rcfile>. A
different programming language can be used for each section, even though this
would complicate inclusion of script from the B<%common> section and
@@ -306,7 +306,7 @@
/usr/local/bin/rc --eval sendmail start | sh
To read the results of a B<OSSP rc> operation without executing or evaluting
-the runcommands, use the 'print' run mode.
+the run-commands, use the 'print' run mode.
/opt/binbin/rc --print --info mico
/usr/local/bin/rc --print httpd reload
@@ -330,7 +330,7 @@
F<rc.conf> - Master configuration file
F<rc.func> - User defined functions library
F<rc.env> - Postprocess variable declaration file
- F<rc.foo> - Runcommands for 'foo' application
+ F<rc.foo> - Run-commands for 'foo' application
=head1 SEE ALSO
|
|
