Commit c568a9fb authored by Nigel Kukard's avatar Nigel Kukard
Browse files

Imported Upstream version 0.0.7

Nigel Kukard <>
This diff is collapsed.
commit def342fdff2d68b234c3091c3443f9778c092caf
Author: Nigel Kukard <>
Date: Tue Sep 9 21:18:22 2014 +0000
Fixed up version reporting on the console
commit 427951ac7c69511df6c76fb963a9146813d4e68f
Author: Nigel Kukard <>
Date: Tue Sep 9 21:12:54 2014 +0000
Fix vim tag so we don't get errors
commit f57c0edc765f22bac91b4c74cea8dc61df29547a
Author: Nigel Kukard <>
Date: Tue Sep 9 20:47:11 2014 +0000
Removed autogenerated files
commit 3f958162b7f19c99418685356932ebf776536bfc
Author: Nigel Kukard <>
Date: Tue Sep 9 20:43:00 2014 +0000
We will only ever support Linux
commit b2ffc04ce7056c08f1f6238cf0a791f5e5fdbca8
Author: Nigel Kukard <>
Date: Tue Sep 9 20:42:34 2014 +0000
We build cputool.8 from doc/ now
commit 377d364431e47ba26fa44bc4420ddd7c9f02f96c
Author: Nigel Kukard <>
Date: Tue Sep 9 20:42:13 2014 +0000
Fixed up manpage generation a bit
commit 99b16e20bc38a2e6e77bd8095e3a73b05696b2cb
Author: Nigel Kukard <>
Date: Tue Sep 9 20:24:22 2014 +0000
Fixed syntax in file
commit e45c49cc7438381e51037f2d3cd16447a621c543
Author: Nigel Kukard <>
Date: Tue Sep 9 20:24:05 2014 +0000
Bumped autoconf version
commit a5da7c3be56df8e8a65d2cd147d652c4e24750c0
Author: Nigel Kukard <>
Date: Tue Sep 9 20:23:32 2014 +0000
Fixed up cputool documentation
commit 3339fe6378a091ae995f3c16b6b9630dece2e996
Author: Nigel Kukard <>
Date: Tue Sep 9 20:11:48 2014 +0000
Updated install file from autotools
commit eb4e84cfe230c9062a16be1801428aacfeea565a
Author: Nigel Kukard <>
Date: Mon Jun 9 20:17:42 2014 +0000
Small whitespace fix
commit 2939866fb93b2b8483cab30371a9f0d48f8a0e89
Author: Nigel Kukard <>
Date: Mon Jun 9 20:16:37 2014 +0000
Bumped copyright year
commit e4117c20bcb4898e1e8c9549eabd38b1bc87d4ca
Author: Nigel Kukard <>
Date: Mon Feb 18 22:11:59 2013 +0000
Better track main process children
commit a4b0003c5a07614a171b034975fa75739f21825f
Author: Nigel Kukard <>
Date: Mon Feb 11 08:37:52 2013 +0000
Continue execution of a process when we exit
* Make sure we continue execution when we exit
* Cleared up some debug info
commit bcf8f67e80008cc44042bfa0a2edf71c388cd6a0
Author: Nigel Kukard <>
Date: Mon Jan 14 22:42:54 2013 +0000
More manpage fixes
commit 5a2c05b4e92f73e486ea0bcdacb47fbae6385fe6
Author: Nigel Kukard <>
Date: Mon Jan 14 22:41:38 2013 +0000
Fixed manpage typo
commit 76d63efbbf65e86bf01a1341f955b942e95132a0
Author: Nigel Kukard <>
Date: Mon Jan 14 17:48:47 2013 +0000
Manpage updates by DLange
Added an examples section and warned people to use -l with TCP network
commit 870b2645c690806e78919b70867a0cea915a6419
Author: Nigel Kukard <>
Date: Mon Jan 14 17:12:56 2013 +0000
Added manpage (woops)
commit 826b9cee8803a51f7406cbf53fd9f9c049e23839
Author: Nigel Kukard <>
Date: Mon Jan 14 17:06:47 2013 +0000
Add manpage to distribution & install
commit d961982b24f01f6ba81d37b3c126f440554a6cf9
Author: Nigel Kukard <>
Date: Mon Jan 14 17:05:41 2013 +0000
Misc cleanups & fixes by DLange
I cleaned up the source a bit, added --version and made the options
parsing (-p / -P and command specified) a bit more robust. I also wrote
a man page.
commit 29dd049894b34162c3e3fdbe4da40085e4939025
Author: Nigel Kukard <>
Date: Thu Jan 10 13:33:11 2013 +0000
Fixed gcc warnings -Thanks Chris C
commit f1e68fea1bb62ab15fed541a3adcb374bc431a79
Author: Nigel Kukard <>
Date: Mon Jan 7 18:35:36 2013 +0000
Convert ticks_delta to 64bit integer
commit a9757a63d8a9153cfbf9a132e886f2a1199385c9
Author: Nigel Kukard <>
Date: Mon Jan 7 18:09:55 2013 +0000
Use proper integer length specifiers in logmsg
commit f07d086d4b941e26e61eaa546ae12c89d9b88df4
Author: Nigel Kukard <>
Date: Mon Jan 7 16:59:38 2013 +0000
Fixed bug with statsTimeDelayed
* Fixed (double) cast, it should be (long double)
* Reduce precision of statsTimeDelayed
commit e3a3af5fc8ba452e6dd5103630e08c9be6652a88
Author: Nigel Kukard <>
Date: Mon Jan 7 13:11:46 2013 +0000
Change of VERSION to tags used by Nigels script
commit 5ab7c37f90dbc88d4c96ccebc58dc4835febca6a
Author: Nigel Kukard <>
Date: Mon Jan 7 13:07:55 2013 +0000
Updated with requirements
commit 6c7dbd904f4bf77644f72573a02da6067eaf436e
Author: Nigel Kukard <>
Date: Sun Jan 6 18:29:59 2013 +0000
Rewrite of PID handling code and /proc walking
commit 612d028cf82aee82d74514a7d8e42cfec848239c
Author: Nigel Kukard <>
Date: Wed Jan 2 19:58:24 2013 +0000
Changed CPU precision from float to double
commit 6951be7ef718696e9f59884a40fa22455dc3ed00
Author: Nigel Kukard <>
Date: Wed Jan 2 19:49:14 2013 +0000
Use tickBucketMax to calculate ticks_allowed, not HZ
commit e9d987088cfbc1ed593fe9ec698dc5f40eb917ec
Author: Nigel Kukard <>
Date: Wed Jan 2 19:38:28 2013 +0000
Change cpuLimit to uint32_t to support many CPU's
commit 46af0327547fedbd7bba35ae2b96a5a1b3c20d3d
Author: Nigel Kukard <>
Date: Wed Jan 2 19:19:04 2013 +0000
Minor fixups (thanks DLange)
* Added support for dynamic tickBucketMax size
* Initialize tickBucket with the max number of ticks allowed
* Error checking on -c/--cpu-limit & -l/--load-limit
* More verbosity on -vv to display our limits
commit 833e40aa5072d155fbeaf6bfceb91d1cf07dcc6e
Author: Nigel Kukard <>
Date: Tue Jan 1 20:13:32 2013 +0000
Remove limits.h
commit 4847acf05ec38c04c4d9597ddc6a717533b9cffd
Author: Nigel Kukard <>
Date: Tue Jan 1 20:11:39 2013 +0000
Better gettime implementation (Thanks DLange)
* Changed gettimeofday to clock_gettime which is monotonic
* Changed integer usage to use uint*_t and other standard types
* Updated to better detect the environment
commit dc0c7d92310c1ce21f8814a7f15b39de272b5006
Author: Nigel Kukard <>
Date: Tue Jan 1 16:56:36 2013 +0000
Fixed 3 bugs reported by DLange
* Proper start CPU time when using -p (and -P)
* Fixed bug where process group CPU time was used instead of process time
* Added documentation for -vvvv
* Fixed bug where the pgid could be killed instead of pid
commit dc3501d88b7092d35e95f72e1beaca37418dd823
Author: Nigel Kukard <>
Date: Mon Dec 31 06:56:21 2012 +0000
Process & process group support
Added support to work on a process or process gorup. We are going to default
to a single PID if specified on the commandline. Not an entire process group.
commit b62058eafe41bb76f362c0fe088e4d05d0b2d0c2
Author: Nigel Kukard <>
Date: Mon Dec 31 06:09:26 2012 +0000
Cleaned up load function
commit 14b363455d2e44358d44388e52bac1eb40e78479
Author: Nigel Kukard <>
Date: Mon Dec 31 00:32:14 2012 +0000
Removed files we don't need in the repo
commit 5aefc6c3a5725b7b89a42e4576a42862fbb1aff7
Author: Nigel Kukard <>
Date: Mon Dec 31 00:29:27 2012 +0000
Added _GNU_SOURCE & -Wall -Werror
commit d0dd187edff6a86eea5f7c1a82d68e1dce0cf2df
Author: Nigel Kukard <>
Date: Sun Dec 30 23:31:00 2012 +0000
Initial commit
Installation Instructions
Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
Basic Installation
Briefly, the shell command `./configure && make && make install'
should configure, build, and install this package. The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package. Some packages provide this
`INSTALL' file but do not implement all of the features documented
below. The lack of an optional feature in a given package is not
necessarily a bug. More recommendations for GNU packages can be found
in *note Makefile Conventions: (standards)Makefile Conventions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. Caching is
disabled by default to prevent problems with accidental use of stale
cache files.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `' (or `') is used to create
`configure' by a program called `autoconf'. You need `' if
you want to change it or regenerate `configure' using a newer version
of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package, generally using the just-built uninstalled binaries.
4. Type `make install' to install the programs and any data files and
documentation. When installing into a prefix owned by root, it is
recommended that the package be configured and built as a regular
user, and only the `make install' phase executed with root
5. Optionally, type `make installcheck' to repeat any self-tests, but
this time using the binaries in their final installed location.
This target does not install anything. Running this target as a
regular user, particularly if the prior `make install' required
root privileges, verifies that the installation completed
6. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
7. Often, you can also type `make uninstall' to remove the installed
files again. In practice, not all packages have tested that
uninstallation works correctly, even though it is required by the
GNU Coding Standards.
8. Some packages, particularly those that use Automake, provide `make
distcheck', which can by used by developers to test that all other
targets like `make install' and `make uninstall' work correctly.
This target is generally not run by end users.
Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'. This
is known as a "VPATH" build.
With a non-GNU `make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
installed the package for one architecture, use `make distclean' before
reconfiguring for another architecture.
On MacOS X 10.5 and later systems, you can create libraries and
executables that work on multiple system types--known as "fat" or
"universal" binaries--by specifying multiple `-arch' options to the
compiler but only a single `-arch' option to the preprocessor. Like
./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CPP="gcc -E" CXXCPP="g++ -E"
This is not guaranteed to produce working output in all cases, you
may have to build one architecture at a time and combine the results
using the `lipo' tool if you have problems.
Installation Names
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX', where PREFIX must be an
absolute file name.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them. In general, the
default for these options is expressed in terms of `${prefix}', so that
specifying just `--prefix' will affect all of the other directory
specifications that were not explicitly provided.
The most portable way to affect installation locations is to pass the
correct locations to `configure'; however, many packages provide one or
both of the following shortcuts of passing variable assignments to the
`make install' command line to change installation locations without
having to reconfigure or recompile.
The first method involves providing an override variable for each
affected directory. For example, `make install
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
`${prefix}'. Any directories that were specified during `configure',
but not in terms of `${prefix}', must each be overridden at install
time for the entire installation to be relocated. The approach of
makefile variable overrides for each directory variable is required by
the GNU Coding Standards, and ideally causes no recompilation.
However, some platforms have known limitations with the semantics of
shared libraries that end up requiring recompilation when using this
method, particularly noticeable in packages that use GNU Libtool.
The second method involves providing the `DESTDIR' variable. For
example, `make install DESTDIR=/alternate/directory' will prepend
`/alternate/directory' before all installation names. The approach of
`DESTDIR' overrides is not required by the GNU Coding Standards, and
does not work on platforms that have drive letters. On the other hand,
it does better at avoiding recompilation issues, and works well even
when some directory options were not specified in terms of `${prefix}'
at `configure' time.
Optional Features
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Some packages offer the ability to configure how verbose the
execution of `make' will be. For these packages, running `./configure
--enable-silent-rules' sets the default to minimal output, which can be
overridden with `make V=1'; while running `./configure
--disable-silent-rules' sets the default to verbose, which can be
overridden with `make V=0'.
Particular systems
On HP-UX, the default C compiler is not ANSI C compatible. If GNU
CC is not installed, it is recommended to use the following options in
order to use an ANSI C compiler:
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
HP-UX `make' updates targets which have the same time stamps as
their prerequisites, which makes it generally unusable when shipped
generated files such as `configure' are involved. Use GNU `make'
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
parse its `<wchar.h>' header file. The option `-nodtk' can be used as
a workaround. If GNU CC is not installed, it is therefore recommended
to try
./configure CC="cc"
and if that doesn't work, try
./configure CC="cc -nodtk"
On Solaris, don't put `/usr/ucb' early in your `PATH'. This
directory contains several dysfunctional programs; working variants of
these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
in your `PATH', put it _after_ `/usr/bin'.
On Haiku, software installed for all users goes in `/boot/common',
not `/usr/local'. It is recommended to use the following options:
./configure --prefix=/boot/common
Specifying the System Type
There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
where SYSTEM can have one of these forms:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf limitation. Until the limitation is lifted, you can use
this workaround:
CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
`configure' Invocation
`configure' recognizes the following options to control how it
Print a summary of all of the options to `configure', and exit.
Print a summary of the options unique to this package's
`configure', and exit. The `short' variant lists options used
only in the top level, while the `recursive' variant lists options
also present in any nested packages.
Print the version of Autoconf used to generate the `configure'
script, and exit.
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
Alias for `--cache-file=config.cache'.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
Use DIR as the installation prefix. *note Installation Names::
for more details, including other options available for fine-tuning
the installation locations.
Run the configure checks, but stop before creating any output
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
AM_CFLAGS = -Wall -Werror