03-17-2011
No. sigaction takes three parameters, not two, and you forgot to save the old structures.
You should also use waitpid(), not wait(), or else you might end up waiting for the wrong child.
9 More Discussions You Might Find Interesting
1. IP Networking
Dear all,
If I login to a Unix system (general user account), will the unix system generate a history file?
If positve, will it stored the IP adress also?
Thanks and Regards
Penny Li
;) (2 Replies)
Discussion started by: PennyLi
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Discussion started by: i2admin
3 Replies
3. Programming
Hello all !
Could someone throw some light on whether there's a limit to the number of characters contained in the command string that is passed to the system() call in C.
Is it OS dependent? If yes, what are the limits for each?
Thanks. (4 Replies)
Discussion started by: vsanjit
4 Replies
4. Solaris
Hello,
I have few questions about file system in Unix and Linux.
1. What's the difference between Unix and Linux in their file system? Are they the same?
2. Is in Unix directory for administrator "/root" - like in Linux - Ubuntu or not?
3.Where is the users directory in Unix? Is it... (2 Replies)
Discussion started by: niki22
2 Replies
5. Programming
in man system it talks about SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored.
Does this signal stuff also happen in popen command?
(even though man popen says nothing about signals)
also if I am not using wait(&status) and I am using waitpid(pid, NULL, 0)
how would... (1 Reply)
Discussion started by: omega666
1 Replies
6. Shell Programming and Scripting
Hi
I have created a perl script & running it using Linux machine. I want my script to die when system command is unsuccessful but script is dying even when system command gets executed successfully. :wall:
I am using the command below :-
system($cmd) || die "FAILED $!";
print "Hello";
... (2 Replies)
Discussion started by: Priyanka Gupta
2 Replies
7. UNIX for Dummies Questions & Answers
I'm currently studying for my exam, and is practicing with sample exam questions.
However there is a question asking "Name THREE UNIX Directory system calls" and the answer given is "opendir, closedir and readdir", however the next question ask "Why is a write directory system call not included... (1 Reply)
Discussion started by: Izzy123
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
The file system unix use a multilevel indexes access to disk, 12 direct blocks, 1 single indirect block, 1 double indirect block, 1 triple indirect block:
Assuming a:
block = 512 bytes,
pointer = 4 byte,
and there is a file of 200 blocks,
how many disk access is needed to read the block... (1 Reply)
Discussion started by: blob84
1 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I am on Solaris 10 server which is running Veritas. It's E420 server with two drives. I don't know much about Veritas. The other guy who works on this, on vacation this week. :-) Any way, looks like I have hard drive issue on the server.
When I do iostat -E. I see this.
sd0... (4 Replies)
Discussion started by: samnyc
4 Replies
WAIT4(2) Linux Programmer's Manual WAIT4(2)
NAME
wait3, wait4 - wait for process to change state, BSD style
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 || _XOPEN_SOURCE >= 500 || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED
wait4():
_BSD_SOURCE
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
4.3BSD.
NOTES
Including <sys/time.h> is not required these days, but increases portability. (Indeed, <sys/resource.h> defines the rusage structure with
fields of type struct timeval defined in <sys/time.h>.)
On Linux, wait3() is a library function implemented on top of the wait4() system call.
SEE ALSO
fork(2), getrusage(2), sigaction(2), signal(2), wait(2), signal(7)
COLOPHON
This page is part of release 3.27 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/.
Linux 2010-09-20 WAIT4(2)