Index: ossp-pkg/rc/00TODO
RCS File: /v/ossp/cvs/ossp-pkg/rc/00TODO,v
rcsdiff -q -kk '-r1.47' '-r1.48' -u '/v/ossp/cvs/ossp-pkg/rc/00TODO,v' 2>/dev/null
--- 00TODO	2003/06/12 13:27:44	1.47
+++ 00TODO	2003/06/23 11:29:44	1.48
@@ -98,6 +98,11 @@
   not contain "%bad", of course. Except: IF ALL rc.* DO NOT
   CONTAIN %bad!
 
+  mlelstv:
+  What we need is some kind of sanity checking. For example, the rc file
+  could prevent a service from beeing started when there is a .rpmsave
+  configuration present.
+
 Change data type locations to private for additional abstraction
   Index: ossp-pkg/cfg/cfg_buf.c
   ============================================================
Index: ossp-pkg/rc/rc.pod
RCS File: /v/ossp/cvs/ossp-pkg/rc/rc.pod,v
rcsdiff -q -kk '-r1.31' '-r1.32' -u '/v/ossp/cvs/ossp-pkg/rc/rc.pod,v' 2>/dev/null
--- rc.pod	2003/05/21 12:49:20	1.31
+++ rc.pod	2003/06/23 11:29:44	1.32
@@ -69,7 +69,8 @@
 =head1 DESCRIPTION
 
 OSSP rc is a run-command processor. Its primary function is to scan F<rcfile>
-script files for B<section>(s) and run the commands listed in the section(s).
+script files for one or more B<section>s and run the commands listed in each
+B<section>.
 
 The run-command processor can alternatively C<print> the commands in human
 readable format or reformat them for shell C<eval> input without executing
@@ -77,14 +78,16 @@
 functionality to query their default, set and effective values.
 
 The structure of the F<rcfile>s is simple but the syntax is highly
-configurable. A F<rcfile> is divided into B<section>s and each of them is
-identified by a label build from the B<section> name. The distribution
-contains various examples.
-
-With a single call to rc usually one F<rcfile> may be processed at, although
-many B<sections> can be passed which are executed in given order. The only
-exception to this rule is when the reserved keyword 'all' is used as F<rcfile>
-meaning 'all F<rcfile>s.'
+configurable. A F<rcfile> is divided into B<section>s, clearly identified by
+applying a regular expression. The default regular expression leads to
+identification of section text starting with a percent (%) and label (any
+text). Various examples of this and other syntax possibilities is given in the
+manpage B<rc(1)>.
+
+Often, only a single B<rcfile> name is processed. To process all B<rcfile>s,
+substitute the keyword 'all' for the B<rcfile> name. The B<section>s of a
+B<rcfil> processed match exactly the B<section>s given on the command line,
+and even the ordering is kept.
 
 =head1 OPTIONS