CFinder for Linux Copyright 2008, Intel Corporation.

This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)


BASIC CFINDER USAGE
-----------------------------------------------------------------------------

Usage: ./cfinder [options]
options:
  Requires exactly one of the following:
    -e, --execute     <"/path/to/executable --with args">
    -p, --pid         <process id>
  The following are optional:
    -c, --countdown   <time (seconds)> (default 0)
    -d, --duration    <time (seconds)> (default 0)
    -l, --log-file    <"logfile.log">
    -r, --report-file <"report.xml">

Examples:
./cfinder --execute "foo -bar" --countdown 20 --report-file myreport.xml
  Launches foo with argument -bar.
  Begins collecting data after 20 seconds.
  Collection stops when SIGINT is received (ctrl-C).
  Log file is written to cfinder-log-timestamp.log in log/ directory.
  Report file is written to myreport.xml in report/ directory.

./cfinder --pid 12345 --duration 42 --log out.xml
  Begins collecting data for process id 12345 immediately.
  Collection stops after 42 seconds.
  Log file is written to out.log in log/ directory.
  Report file is written to cfinder-summary-timestamp.xml in report/ directory.

ENABLING AND DISABLING CORES FOR LINUX
-----------------------------------------------------------------------------

Disabling cores on Linux can be done by passing "maxcpus=1" to the "kernel" 
line in grub, either at boot time, or by editing menu.lst. 

If the lilo boot loader is used, maxcpus=1 should be appended to the 
lilo.conf file. If the file is edited, the system will need to be rebooted.

To restore the cores, simply remove any changes that were made to the boot
process.

THIRD PARTY LICENSES
-----------------------------------------------------------------------------

OpenSSL License
---------------

/* ====================================================================
 * Copyright (c) 1998-2008 The OpenSSL Project.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in
 *    the documentation and/or other materials provided with the
 *    distribution.
 *
 * 3. All advertising materials mentioning features or use of this
 *    software must display the following acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
 *
 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
 *    endorse or promote products derived from this software without
 *    prior written permission. For written permission, please contact
 *    openssl-core@openssl.org.
 *
 * 5. Products derived from this software may not be called "OpenSSL"
 *    nor may "OpenSSL" appear in their names without prior written
 *    permission of the OpenSSL Project.
 *
 * 6. Redistributions of any form whatsoever must retain the following
 *    acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
 *
 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 * OF THE POSSIBILITY OF SUCH DAMAGE.
 * ====================================================================
 *
 * This product includes cryptographic software written by Eric Young
 * (eay@cryptsoft.com).  This product includes software written by Tim
 * Hudson (tjh@cryptsoft.com).
 *
 */