OSSP CVS Repository

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

ossp-pkg/rc/rc.pod 1.36 -> 1.37

--- rc.pod       2003/06/23 15:46:05     1.36
+++ rc.pod       2003/06/23 16:44:55     1.37
@@ -124,7 +124,7 @@
 
 specify the location of one or more optional function files. They act like
 libraries, containing commands which are prepended to the sections of their
-corresponding C<rcfile>s just before execution.
+corresponding F<rcfile>s just before execution.
 
 =item B<-h>|B<--help>
 
@@ -264,27 +264,26 @@
 
 =head1 ERROR HANDLING
 
-Rich and fine-tuned error handling is possible by writing one or both of the
-following sections into F<rcfile>(s). These sections typically reference the
-local F<rcfile>'s variables ${rc_errcode} and ${rc_errstring} for more
-information about which error was encountered and its text.
+Fine-tuned error handling is possible by writing one or both of the following
+section labels into an F<rcfile>. These sections typically reference the local
+F<rcfile>'s variables ${rc_errcode} and ${rc_errstring} for more information
+about which error was encountered and its text.
 
 =item B<%error>
 
 If an error condition arises during an F<rcfile>'s processing, control will
 pass to the B<%error> section whose commands will begin to run. Should no such
-B<%error> section exist, rc will stop any rcfile processing and write error
-strings to the console and syslog using LOG_USER and LOG_ERR (see syslog(3)).
-An empty B<%error> section in each F<rcfile> is synonymous to a
-C<IgnoreAllErrors> option (which doesn't exist).
+B<%error> section exist, rc will stop processing and write error strings to
+the console and syslog using LOG_USER and LOG_ERR (see syslog(3)). An empty
+B<%error> section in each F<rcfile> will cause errors to be ignored. In any
+case of error however, rcfile processing will stop.
 
 =item B<%default>
 
 The commands in the B<%default> section are run when the corresponding
 F<rcfile> contains no section label matching the one(s) specified on the
 command line. If the appropriate section label doesn't exist and neither does
-B<%default>, then an error is assumed and control flows to the B<%error>
-section.
+B<%default>, then nothing happens and processing silently procedes.
 
 =head1 EXAMPLES
 
@@ -313,7 +312,7 @@
  /opt/binbin/rc --print --info mico
  /usr/local/bin/rc --print httpd reload
 
-Arguments in the form of name=value pairs may be passed to the section(s)
+Arguments in the form of name=value pairs may be passed to the B<sections>
 given on the command line. In the F<rcfile>, such arguments will appear as
 normal configuration variables. They can be referenced as such (by default as
 ${myarg}). On the command line, the arguments following a section will be
@@ -337,8 +336,8 @@
 =head1 SEE ALSO
 
 OSSP rc integrates concepts taken from other run-command architectures. For
-more information, inspect the /etc/rc structures provided by the NetBSD,
-FreeBSD, Solaris, and Red Hat distributions.
+more information, inspect the /etc/rc? structures provided by the NetBSD,
+FreeBSD, Solaris, and Linux distributions.
 
 rc-sample(5).
 

CVSTrac 2.0.1