A BSD-style wait4 implementation.

Using existing code from the posixmodule.c and
resource.c files,
I threw together a patch that implements the wait4
function.

This function is similar to waitpid, but it also
returns usage information
about the child process.

wait4(pid, options) -> (pid, status, rusage)

It works for me on RedHat Linux 9 and FreeBSD 4.5 boxes
using
Python-2.3.4.

The patch may need some fine tuning.

Thanks
Chad

Logged In: YES 
user_id=2772

You should also add code to the test suite to test wait4
when it is available.

Logged In: YES 
user_id=1093928

Added a test suite and an example of using wait4.  Feedback
is welcome.
Thanks.

Logged In: YES 
user_id=21627

struct rusage is already defined in
Modules/resourcemodule.c. It would be good if there was only
a single definition of the type object.

To achieve this, resourcemodule.c should expose a C API (e.g. 

  PyObject *PyResource_FromResource(struct rusage*)

). This should be put into a CObject, which should be
published through the module; then posixmodule should import
resource when wait4 is called for the first time.

Alternative, wait4 could be added to resourcemodule.c entirely.

Yet another alternative, on top of this approach,
posixmodule and/or os.py could provide their own definition
of wait4 which delegates to resource.wait4 on first usage.

Logged In: YES 
user_id=1093928

Finally took the time to implement os.wait4 based the
comments from
loewis.  Added a resourcemodule.h header and modified
resource.c and
posixmodule.c appropriately.

Take a gander and let me know what you think.
Thanks.

Logged In: YES 
user_id=21627

The code looks fine. The only problem I have with it that it
seems to assume that any POSIX system implements wait4.
However, I don't see it in Single Unix V3, so I think there
should be some configure test to determine whether the
function is present.

Also, it would be nice if the resource module was only
imported if wait4 was actually called.

I can't see documentation changes; please provide a patch
for Doc/lib/libos.tex as well.

If you resubmit the patch, it would be easiest if the patch
was a single file, eg. generated with "cvs diff -u". There
is no need to include configure changes; configure.in would
be sufficient.

Logged In: YES 
user_id=1093928

Per Martin's suggestions - thanks again.
Documentation additions, configure test, import when called,
single diff.

LMK how this one fairs.

Logged In: YES 
user_id=1093928

Fix compilation error (gcc-2.95).

Has anyone had a chance to look at this for inclusion?

Logged In: YES 
user_id=33168

Dup: 1309579.  Not sure which is most up-to-date.  Waiting
for Chad to advise.

Logged In: YES 
user_id=33168

Received mail from author, this is out of date, newer patch
is up-to-date.