Michael Shields <mjshield@nyx.cs.du.edu>
Charles Blake <cblake@bbn.com>
David Mossberger-Tang
-Albert Cahalan <acahalan@cs.uml.edu>
+Albert Cahalan <albert@users.sf.net>
skill/kill/snice:
-Albert Cahalan <acahalan@cs.uml.edu>
+Albert Cahalan <albert@users.sf.net>
tload:
Branko Lankester
Where to send
=============
-Send comments, bug reports, patches, etc., to acahalan@cs.uml.edu
+Send comments, bug reports, patches, etc., to albert@users.sf.net
What to send
============
-It is much more useful to me if a program really crases to recompile it
+It is much more useful to me if a program really crashes to recompile it
with make "CC=gcc -ggdb -O", run it with "gdb prog" and "run" and send
me a stack trace ('bt' command). That said, any bug report is still
better than none.
+strace and ltrace output are very helpful:
+
+ strace -o output-file ps --blah
+ bzip2 output-file
+
It might be nice to get rid of miscellaneous compiler warnings, but
don't bend over backwards to do it.
A macro is provide in libproc/version.h to construct the code from its
components, e.g.
- if (linux_version_code < LINUX_VERSION(1,1,30))
- /* tty field is only a minor */
+ if (linux_version_code < LINUX_VERSION(2,5,41))
+ /* blah blah blah */
A startup call to set_linux_version may also be necessary.
Of course, if a bug is due to a change in kernel file formats, it would
be best to first try to generalize the parsing, since the code is then
more resilient against future change.
-If you send me patches which are specific to *compiling* on a particular
-version of Linux include a "#if LINUX_VERSION_CODE > 1*0x10000+3*0x100+54"
-markup of the patch so that the package may be compiled with older
-kernels as well as the "latest and greatest". LINUX_VERSION_CODE is
-#define'd in <linux/version.h>.
-
-Note that you should not make patches specific to *compiling* on a
-particular version of Linux unless there is nothing else you can do.
-
Also unified diffs (diff -u) are my preference, context diffs (diff -c )
are kind of usable, and standard diffs (diff) are more useless than a
generic text description of what you did. Just use
- diff -u oldfile newfile
+ diff -Naurd oldfile newfile
or
- diff -Naur old-procps-dir new-procps-dir
+ diff -Naurd old-procps-dir new-procps-dir
to create your diffs and you will make me happy. Also make sure to
include a description of what the diff is for or I'm likely to ignore
it because of general lack of time...
Code Structure
==============
-My ultimate goal for this package is to be compilable with any kernel
-headers and to be able to run under any kernel's /proc. (Don't bother
-telling me that I'm not especially close to my ultimate goal... who
-is? :-)
-Anyhow, another goal is to encapsulate *all* parsing dependent on /proc
+A goal is to encapsulate *all* parsing dependent on /proc
file formats into the libproc library. If the API is general enough
it can hopefully stabilize and then /proc changes might only require
updating libproc.so. Beyond that having the set of utilities be simple
.SH AUTHORS
Written by Brian Edmonds.
-Send bug reports to <acahalan@cs.uml.edu>
+Send bug reports to <albert@users.sf.net>
This command meets appropriate standards. The -L flag is Linux-specific.
.SH AUTHOR
-Albert Cahalan <acahalan@cs.uml.edu> wrote kill in 1999 to replace the
+Albert Cahalan <albert@users.sf.net> wrote kill in 1999 to replace the
version that was not standards compliant. Michael K. Johnson
<johnsonm@redhat.com> is the current maintainer of the procps collection.
-Please send bug reports to <acahalan@cs.uml.edu>
+Please send bug reports to <albert@users.sf.net>
Keywords: procps /proc libproc
ps uptime tload free w top vmstat watch skill snice kill pgrep pkill
Author: Michael K. Johnson, Charles Blake, Albert Cahalan, many others.
-Maintained-by: various <acahalan@cs.uml.edu>
+Maintained-by: various <albert@users.sf.net>
Primary-site: http://procps.sf.net/
185kB procps-3.0.0.tar.gz
Alternate-site: http://www.debian.org/Packages/unstable/base/procps.html
No standards apply.
.SH AUTHOR
-Albert Cahalan <acahalan@cs.uml.edu> wrote skill and snice in 1999 as a
-replacement for a non-free version. Michael K. Johnson <johnsonm@redhat.com>
-is the current maintainer of the procps collection.
-
-Please send bug reports to <acahalan@cs.uml.edu>
+Albert Cahalan <albert@users.sf.net> wrote skill and snice in 1999 as a
+replacement for a non-free version, and is the current maintainer of the
+procps collection. Please send bug reports to <albert@users.sf.net>
Branko Lankester, David Engel <david@ods.com>, and
Michael K. Johnson <johnsonm@redhat.com>.
-Please send bug reports to <acahalan@cs.uml.edu>
+Please send bug reports to <albert@users.sf.net>
Bugs? What bugs? But, if ever there were, then...
Please send bug reports to:
- Albert D\. Cahalan, <acahalan@cs.uml.edu>
+ Albert D\. Cahalan, <albert@users.sf.net>
[ thanks Albert, heaven forbid author should be bothered ]
With invaluable help from:
Craig Small, <csmall@small.dropbear.id.au>
- Albert D\. Cahalan, <acahalan@cs.uml.edu>
+ Albert D\. Cahalan, <albert@users.sf.net>
.ig
.rj 2
*/
/* For their contributions to this program, the author wishes to thank:
* Craig Small, <csmall@small.dropbear.id.au>
- * Albert D. Cahalan, <acahalan@cs.uml.edu>
+ * Albert D. Cahalan, <albert@users.sf.net>
*/
#include <sys/ioctl.h>
#include <sys/resource.h>
*/
/* For their contributions to this program, the author wishes to thank:
* Craig Small, <csmall@small.dropbear.id.au>
- * Albert D. Cahalan, <acahalan@cs.uml.edu>
+ * Albert D. Cahalan, <albert@users.sf.net>
*/
#ifndef _Itop
#define _Itop
was written by Larry Greenfield <greenfie@gauss.rutgers.edu> and
Michael K. Johnson <johnsonm@sunsite.unc.edu>.
-Please send bug reports to <acahalan@cs.uml.edu>
+Please send bug reports to <albert@users.sf.net>
.SH "SEE ALSO"
.BR ps (1),
.BR top (1),
Greenfield <greenfie@gauss.rutgers.edu> and Michael K. Johnson
<johnsonm@redhat.com>.
-Please send bug reports to <acahalan@cs.uml.edu>
+Please send bug reports to <albert@users.sf.net>