Changeset 1803 for zzuf/trunk


Ignore:
Timestamp:
Jul 10, 2007, 5:42:37 PM (13 years ago)
Author:
Sam Hocevar
Message:
  • Documented the new -T / --max-cpu flag.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • zzuf/trunk/doc/zzuf.1

    r1800 r1803  
    77       [\fB\-f\fR \fIfuzzing\fR] [\fB\-D\fR \fIdelay\fR] [\fB\-F\fR \fIforks\fR] [\fB\-C\fR \fIcrashes\fR] [\fB\-B\fR \fIbytes\fR]
    88.br
    9        [\fB\-t\fR \fIseconds\fR] [\fB\-M\fR \fImegabytes\fR] [\fB\-P\fR \fIprotect\fR] [\fB\-R\fR \fIrefuse\fR]
    10 .br
    11        [\fB\-p\fR \fIpick\fR] [\fB\-b\fR \fIranges\fR] [\fB\-I\fR \fIinclude\fR] [\fB\-E\fR \fIexclude\fR]
     9       [\fB\-t\fR \fIseconds\fR] [\fB\-T\fR \fIseconds\fR] [\fB\-M\fR \fImegabytes\fR] [\fB\-b\fR \fIranges\fR]
     10.br
     11       [\fB\-P\fR \fIprotect\fR] [\fB\-R\fR \fIrefuse\fR] [\fB\-p\fR \fIpick\fR] [\fB\-I\fR \fIinclude\fR] [\fB\-E\fR \fIexclude\fR]
    1212.br
    1313       [\fIPROGRAM\fR [\fB\-\-\fR] [\fIARGS\fR]...]
     
    6060Automatically terminate child processes that output more than \fIn\fR bytes
    6161on the standard output and standard error channels. This is useful to detect
    62 infinite loops. See also the \fB\-t\fR flag.
     62infinite loops. See also the \fB\-t\fR and \fB\-T\fR flags.
    6363.TP
    6464\fB\-c\fR, \fB\-\-cmdline\fR
     
    259259Automatically terminate child processes that run for more than \fIn\fR
    260260seconds. This is useful to detect infinite loops or processes stuck in other
    261 situations. See also the \fB\-B\fR flag.
     261situations. See also the \fB\-B\fR and \fB\-T\fR flags.
     262.TP
     263\fB\-T\fR, \fB\-\-max\-cpu\fR=\fIn\fR
     264Automatically terminate child processes that use more than \fIn\fR seconds
     265of CPU time.
     266
     267\fBzzuf\fR uses the \fBsetrlimit\fR() call to set CPU usage limitations and
     268relies on the operating system's ability to enforce such limitations. If the
     269system sends \fBSIGXCPU\fR signals and the application catches that signal,
     270it will receive a \fBSIGKILL\fR signal after 5 seconds.
     271
     272This is more accurate than \fB\-t\fR because the behaviour should be
     273independent from the system load, but it does not detect processes stuck into
     274infinite \fBselect\fR() calls because they use very little CPU time. See also
     275the \fB\-B\fR and \fB\-t\fR flags.
    262276.TP
    263277\fB\-v\fR, \fB\-\-verbose\fR
Note: See TracChangeset for help on using the changeset viewer.