[netfilter-cvslog] r3410 - trunk/nfsim/core
jk at netfilter.org
jk at netfilter.org
Thu Dec 16 06:56:29 CET 2004
Author: jk at netfilter.org
Date: 2004-12-16 06:56:28 +0100 (Thu, 16 Dec 2004)
New Revision: 3410
Modified:
trunk/nfsim/core/core.c
Log:
Documentation cleanups, add --usage
Modified: trunk/nfsim/core/core.c
===================================================================
--- trunk/nfsim/core/core.c 2004-12-16 05:45:05 UTC (rev 3409)
+++ trunk/nfsim/core/core.c 2004-12-16 05:56:28 UTC (rev 3410)
@@ -215,6 +215,14 @@
<subtitle>Print the version of the simulator and kernel</subtitle>
</section>
*/
+ {"usage", 0, 0, 'u'},
+/*** XML Argument:
+ <section id="a:usage">
+ <title><option>--usage</option></title>
+ <subtitle>Print usage information</subtitle>
+ <para>Causes nfsim to print its command line arguments and then exit</para>
+ </section>
+*/
{"failtest", 0, 0, 1},
/*** XML Argument:
<section id="a:failtest">
@@ -222,10 +230,11 @@
<subtitle>Try every combination of external failures</subtitle>
<para>This option will <function>fork()</function> the simulator
whenever a possible failure point is reacked (eg
- <function>kmalloc</function>. The child process will fail the function,
- while the parent will succeed. If the simulator reaches an error, the
- pattern of successes/failures will be printed out, which can be replayed
- using <option>--failpattern</option></para>
+ <function>kmalloc</function>). The child process will fail the function,
+ while the parent will succeed. If the simulator reaches an error (other
+ than a script failure - these can be reasonable behaviour) the pattern of
+ successes/failures will be printed out, which can be replayed using
+ <option>--failpattern</option></para>
</section>
*/
@@ -271,6 +280,11 @@
print_license();
exit(EXIT_SUCCESS);
break;
+ case 'u':
+ print_license();
+ print_usage(argv[0]);
+ exit(EXIT_SUCCESS);
+ break;
case 1:
failtest = true;
break;
More information about the netfilter-cvslog
mailing list