OSSP CVS Repository

ossp - Difference in ossp-pkg/rc/rc.pod versions 1.34 and 1.35
Not logged in
[Honeypot]  [Browse]  [Home]  [Login]  [Reports
[Search]  [Ticket]  [Timeline
  [History

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
 

CVSTrac 2.0.1