Man pages
PDF Print E-mail

festival - Linux Command

       festival [options] [file0] [file1] ...

       Festival is a general purpose text-to-speech system.  As well as simply
       rendering text as speech it can be used in an interactive command  mode
       for testing and developing various aspects of speech synthesis technol-

       Festival has two major modes, command and tts  (text-to-speech).   When
       in  command  mode  input (from file or interactively) is interpreted by
       the command interpreter.  When in tts mode input is rendered as speech.
       When  in  command mode filenames that start with a left paranthesis are
       treated as literal commands and evaluated.

       -q      Load no default setup files

       --libdir <string>
               Set library directory pathname

       -b      Run in batch mode (no interaction)

       --batch Run in batch mode (no interaction)

       --tts   Synthesize text in files as speech no  files  means  read  from
               stdin (implies no interaction by default)

       -i      Run in interactive mode (default)

               Run in interactive mode (default)

       --pipe  Run in pipe mode, reading commands from stdin, but no prompt or
               return values are printed (default if stdin not a tty)

       --language <string>
               Run in named language, default is english,  spanish  and  welsh
               are available

               Run in server mode waiting for clients of server_port (1314)

               <ifile>  Used  in  #!  scripts,  runs in batch mode on file and
               passes all other args to Scheme

       --heap <int> {1000000}
               Set size of Lisp heap, should not normally need to  be  changed

       Although we cannot guarantee the time required to fix  bugs,  we  would
       appreciated it if they were reported to

       Alan W Black, Richard Caley and Paul Taylor
       (C) Centre for Speech Technology Research, 1996-1998
       University of Edinburgh
       80 South Bridge
       Edinburgh EH1 1HN

                                 6th Apr 1998                      FESTIVAL(1)

Linux Help documents. These manual pages will also work for Red Hat 5.2
Man(1) output converted with man2html
PDF Print E-mail

ftrace - Linux Command

       ftrace [-c] [-i] [-m] [-o=FILE] [-p=PID...] [-sys=SYSCALL[,SYSCALL...]]
              [-sig=SIG[,SIG...]] [-plt=RULE[,RULE...]] [-dyn=RULE[,RULE...]]
              [-sym=RULE[,RULE...]] [-stack] [--] command [arguments...]

       ftrace starts given command and according to tracing script given via
       command-line arguments, it traces its system calls, symbol entry points
       in general, and possibly other events as well. It uses the Frysk
       framework to implement tracing.

       The working set of events ftrace should trace is defined by the
       following arguments.

   Process Selection Options
       -p=PID Attach to a process with given PID.

       -c     Trace children: automatically attach to forks of traced process.

   System Call and Signal Tracing
              Trace system calls that match given SYSCALL ruleset. See below
              for description of SYSCALL syntax.

              Trace signals that match given SIGNAL ruleset. See below for
              description of SIGNAL syntax.

       -stack Stack trace when traced system call is hit. Note that this
              option also applies to traced symbols. If you need to
              cherry-pick which event should stack trace, use # operator
              described in sections below.

   Symbol Tracing
       -i     Trace inside dynamic linker. When this option is not present,
              ftrace will function as if -@INTERP rule was present at the end
              of each tracing script.

              Trace library calls done via PLT entries matching each given
              SYMBOL ruleset. By tracing PLT entry, you effectively trace
              calls done FROM given library or executable, and generally can’t
              say which library the call leads TO. (At least for now. Ftrace
              may grow brains for this in future.) See below for description
              of SYMBOL rule syntax.

              Trace calls through the symbol entry points. By tracing entry
              points, you catch all calls that end up at this symbol,
              including the calls that don’t go through PLT and as such are
              not intended as inter-library calls, but rather intra-library
              calls. This is probably not what you usually want, because you
              which event should stack trace, use # operator described in
              sections below.

   Other Traceable Events
       -m     Print each file mapped to or unmapped from address space of the
              traced process.

       To decide which PLT slots or entry points should be traced, following
       process takes place. Initial working set is empty. Rules, if present,
       are then enumerated from left to right, and set is modified depending
       on the rules. Rules are delimited by a colon. Syntax of each rule is


       Optional "-" at the beginning of the rule means removal from the
       working set. When the sign is omitted, the default action is to add to
       the working set. Optional "#" means that ftrace should print out stack
       trace when it hits the call. The combination of "-#" then means that
       the call should still be traced, but stack trace shouldn’t be
       generated.  pattern defines which PLT entries from which libraries
       should be added or removed from working sennt. Syntax of pattern is the


       All three components, symbol, soname and version, are written using
       extended regular expression syntax. Any of the components can be
       omitted, missing component is then wild card matching anything. By
       extension, empty pattern matches all symbols of all versions in all
       libraries and in the executable itself.

       symbol component is matched against name of symbol associated with PLT
       slot under consideration. Whole symbol name has to match.

       soname component is matched against a soname of a library in which we
       wish to track the call. If the library has no associated soname or it
       is a main executable, the match is done against the file name (without
       a path). Two special sonames are distinguished: "MAIN", which always
       matches main executable; and "INTERP", which always matches ELF
       interpreter of the main executable.

       version component is matched against version associated with symbol. If
       the symbol has no associated version, it is considered to be an empty
       string. (It is possible to request symbol without a version with the
       pattern "foo@@".)

       Empty rule is considered to miss all components.

       Under the presence of the -sys (or -sig) option, ALL system calls (or

       When the pattern is empty, then it matches all events known to frysk.
       When the pattern is simple number (e.g. "12"), then the pattern matches
       the event with the given number. Otherwise the pattern is considered to
       be case-insensitive glob, and matched against event names. Whole name
       has to match for event to be part of working set.

       Signal can be given both with and without leading "sig" (e.g. "sigkill"
       as well as "kill").

       Trace all system calls:

       ftrace -sys= ls

       Trace variants of stat system call and moreover a system call #3:

       ftrace -sys=â€â€™*stat*,3â€â€™ ls

       Various ways to tell ftrace that you want to stack trace on SIGUSR1:

       ftrace -sig=#USR1,#usr1,#SIGUSR1,#sigusr1,#10 ~/sig

       Trace all library calls:

       ftrace -plt= ls

       Trace all library calls to functions that contain substring "write" in
       their names:

       ftrace -plt=â€â€™*write*â€â€™ ls

       Trace memory functions done from libraries, i.e. not from main

       ftrace -plt=â€â€™[cm]alloc|free,-@MAINâ€â€™ ls

       Stack trace on everything, except for memory allocation functions
       (which should still be traced):

       ftrace -plt=â€â€™#,-#[cm]alloc,-#freeâ€â€™ ls


       The option parser is greedy when looking for options so running ftrace
       on a program that uses options can be a problem, use -- to split
       between ftrace and the program. So change from:

       ~/prefix/bin/ftrace ~/prefix/lib64/frysk/funit --arch 32 frysk.proc.TestAbandon

Linux Help documents. These manual pages will also work for Red Hat 5.2
Man(1) output converted with man2html
PDF Print E-mail

foomatic-printjob - Linux Command


       foomatic-printjob [ -s spooler ] [ -P queuename ] [  -o  option1=value1
       -o option2 ... ] [ -i ] [ file1 file2 ... ]

       foomatic-printjob  -Q  [  -s spooler ] [ -P queuename ] [ -i ] [ -a ] [
       user1 user2 ... ]

       foomatic-printjob -R [ -s spooler ] [ -P queuename ]  [  -i  ]  [  -  |
       jobid1 jobid2 ... ]

       foomatic-printjob -C [ -s spooler ] [ -i ] command [ arguments ]

       foomatic-printjob -S [ -s spooler ] [ -i ]

       foomatic-printjob -h [ -s spooler ] [ -P queuename ] [ -i ]

       foomatic-printjob  provides a spooler-independent interface to creating
       and managing printer jobs and print queues.  Note that the first  argu-
       ment  changes the mode of the command, as it combines the functionality
       of several System V-style printing commands.

       -sspooler Explicit spooler type.

                 Any commands specified should apply to this queue instead  of
                 the default.

                 Set option to value

       -ooption  Set the switch option

       -#n       Print n copies

       file1  file2  ...
                 Files  to  be  printed, when no file is given, standard input
                 will be printed

       -Q        Query the jobs in a queue.  If a list of users is  specified,
                 only those users’ jobs will be queried.

                 same commands given under  different  spoolers  do  the  same

       -i        Interactive  mode:  You will be asked if foomatic-printjob is
                 in doubt about something.  Otherwise  foomatic-printjob  uses
                 auto-detection or quits with an error.

       -S        Save the chosen spooler as the default spooler

       -h        Show  this  message  or show a list of available options if a
                 queue is specified

       foomatic-configure(1) and the documentation for your print spooler.

       Manfred  Wassmann  <>  and  Chris  Lawrence
       <>  for  the  foomatic project using output from the
       associated binary.

       This manpage still needs some editing.

Foomatic Project                  2001-01-06              FOOMATIC-PRINTJOB(1)

Linux Help documents. These manual pages will also work for Red Hat 5.2
Man(1) output converted with man2html
PDF Print E-mail

foomatic-perl-data - Linux Command

       foomatic-perl-data  [ -O ] [ -C ] [ -P ] [ -D ] [ -o option=setting ] [
       -o ... ] [ -v ] [ filename ]

       -O Parse overview XML data

       -C Parse printer/driver combo XML data (default)

       -P Parse printer entry XML data

       -D Parse driver entry XML data

       -o option=setting Default option settings for the generated  Perl  data
       (combo only)

       -v Verbose (debug) mode

       filename Read input from a file and not from standard input

       foomatic-perl-data returns ...

       Manfred   Wassmann   <>  for  the  foomatic
       project using output from the associated binary.

       This manpage needs editing.

Foomatic Project                  2002-04-22             FOOMATIC-PERL-DATA(1)

Linux Help documents. These manual pages will also work for Red Hat 5.2
Man(1) output converted with man2html
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>

Page 3 of 37