TUX: Penguin Power!
Linux| Perl| PHP| Webserv| Databases| Sysadmin| Programming| Filesystems| Java| Webprog

Make Tux happy: Link to us!


SYNOPSIS
       #include <sys/types.h>
       #include <sys/time.h>
       #include <sys/resource.h>
       #include <sys/wait.h>

       pid_t wait3(int *status, int options,
                   struct rusage *rusage);

       pid_t wait4(pid_t pid, int *status, int options,
                   struct rusage *rusage);

   feature test macro requirements for glibc (see feature_test_macros(7)):

       wait3(): _BSD_SOURCE
       wait4(): _BSD_SOURCE || _XOPEN_SOURCE >= 500

DESCRIPTION
       the  wait3()  and  wait4()  system calls are similar to waitpid(2), but
       additionally return resource usage information about the child  in  the
       structure pointed to by rusage.

       Other than the use of the rusage argument, the following wait3() call:

           wait3(status, options, rusage);

       is equivalent to:

           waitpid(-1, status, options);

       Similarly, the following wait4() call:

           wait4(pid, status, options, rusage);

       is equivalent to:

           waitpid(pid, status, options);

       In  other  words, wait3() waits of any child, while wait4() can be used
       to select a specific child, or children, on which to wait.  see wait(2)
       for further details.

       If  rusage  is  not  NULL, the struct rusage to which it points will be
       filled with accounting information about the child.   see  getrusage(2)
       for details.

RETURN VALUE
       as for waitpid(2).

ERRORS
       as for waitpid(2).

CONFORMING TO

COLOPHON
       This page is part of release 3.23 of the Linux  man-pages  project.   A
       description  of  the project, and information about reporting bugs, can
       be found at http://www.kernel.org/doc/man-pages/.



Find all the song lyrics here: Lyrics Now!