Sponsored Content
Full Discussion: [C]Fork and waitpid
Top Forums Programming [C]Fork and waitpid Post 302580778 by lamachejo on Friday 9th of December 2011 02:26:57 PM
Old 12-09-2011
[C]Fork and waitpid

Hi folks, I am writing a simple program to understand how fork() and waitpid works, but it doesn't seem that is working like I wanted.

Code:
if(fork()==0){
	//el hijo
	pid1=getpid();
	printf("\nSoy el hijo %d",pid1);
}else {
	//el padre
	if (fork()==0) {
		//el hijo
		pid2=getpid();
		printf("\nSoy el hijo %d",pid2);
		 }
	else {
             .... more forks....

the father (last else)
else{
					// el padre
					// espera el hijo 1
					waitpid(pid1,status1,0);
					hijos--;
					printf("\nacaba de finalizar mi hijo con PID %d",pid1);
					//espera al hijo 2
					waitpid(pid2,status2,0);
					hijos--;
					printf("\nacaba de finalizar mi hijo con PID %d",pid2);

One of the problems I have encountered is that the printed PID by the father does not correspond to any of the childs (sometimes 0 is printed).

The other one is that the fater doesn't wait for the childs, the message "acaba de finalizar..." will pop out first than " soy el hijo...", and what I want is for the father to wait for the child to finish, and once is finished, print that the child with PID X has finished.
 

10 More Discussions You Might Find Interesting

1. Programming

fork()

#include <stdio.h> #include <string.h> #include <sys/types.h> #define MAX_COUNT 200 #define BUF_SIZE 100 void main(void) { pid_t pid; int i; char buf; fork(); pid = getpid(); for (i = 1; i <= MAX_COUNT; i++) { sprintf(buf,... (2 Replies)
Discussion started by: MKSRaja
2 Replies

2. Programming

Fork or what?

Hello all. I'm developing a filetransfer application, which is supposed to work sort of like dcc, with multiple transfers etc. Now i wonder what the best way to manage the transfers is. Should i fork() for each new transfer, hogging loads of memory or use pthreads? Maybe I can use select to see... (0 Replies)
Discussion started by: crippe
0 Replies

3. Programming

problems with FORK() and WAITPID()

Dear All, I'm trying to write multithreading TCP Daemon which executes external program when new network connection arrives on a socket. After accept() I'm doing fork() for initiating of new child process, in which will be executed external program. After child creation I'm doing fork() again,... (3 Replies)
Discussion started by: Polkovnik
3 Replies

4. Programming

Fork ()

hi all About this code for (i = 1; i < n; i++) if ((childpid = fork()) <= 0) break; I really can't understand the output . and the way fork () return the value . how about the process Id ,the child process Id and the parent ID in this case so please answer me soon (5 Replies)
Discussion started by: iwbasts
5 Replies

5. Programming

fork() help

Hi everybody, I wanna write a code to understand how fork works. my target -------------- -Parent creates a file(called temp) and writes into this file "1".Then it closes the file. -Then parent creates a child and wait until execution of this child ends. -Then child opens the same... (3 Replies)
Discussion started by: alexicopax
3 Replies

6. Programming

Fork()

does fork() spawn only the parent process, what if fork() is looped, does it spawn the parent and the child? (4 Replies)
Discussion started by: Peevish
4 Replies

7. UNIX for Dummies Questions & Answers

fork()

I'm trying to run a simple test on how to use fork(), i'm able to execute the child process first then the parent, but how can I execute parent then child..? Thanks! (1 Reply)
Discussion started by: l flipboi l
1 Replies

8. Programming

waiting for multiple childs - C - waitpid

Hi gurus, I would like to fork more children and then write their return values: so far I tried: #include <stdio.h> #include <stdlib.h> #include <errno.h> #include <unistd.h> #include <sys/types.h> #include <sys/wait.h> int main(void) { pid_t pid; int rv=0, i; ... (5 Replies)
Discussion started by: wakatana
5 Replies

9. Programming

waitpid and grandchildren

I'm attempting to write a daemon that will start, stop, and monitor processes across a network of servers, meaning that a daemon would start on each server, attempt to connect to siblings at regular intervals (if there are unconnected siblings), and start services as remote dependencies are... (3 Replies)
Discussion started by: kshots
3 Replies

10. Programming

Fork!

I understand that fork create a child but I need very simple example that make child useful.... I mean how will make the program faster anyone explain with code plz using C plz (2 Replies)
Discussion started by: fwrlfo
2 Replies
KCMP(2) 						     Linux Programmer's Manual							   KCMP(2)

NAME
kcmp - compare two processes to determine if they share a kernel resource SYNOPSIS
#include <linux/kcmp.h> int kcmp(pid_t pid1, pid_t pid2, int type, unsigned long idx1, unsigned long idx2); Note: There is no glibc wrapper for this system call; see NOTES. DESCRIPTION
The kcmp() system call can be used to check whether the two processes identified by pid1 and pid2 share a kernel resource such as virtual memory, file descriptors, and so on. Permission to employ kcmp() is governed by ptrace access mode PTRACE_MODE_READ_REALCREDS checks against both pid1 and pid2; see ptrace(2). The type argument specifies which resource is to be compared in the two processes. It has one of the following values: KCMP_FILE Check whether a file descriptor idx1 in the process pid1 refers to the same open file description (see open(2)) as file descriptor idx2 in the process pid2. The existence of two file descriptors that refer to the same open file description can occur as a result of dup(2) (and similar) fork(2), or passing file descriptors via a domain socket (see unix(7)). KCMP_FILES Check whether the processes share the same set of open file descriptors. The arguments idx1 and idx2 are ignored. See the discus- sion of the CLONE_FILES flag in clone(2). KCMP_FS Check whether the processes share the same filesystem information (i.e., file mode creation mask, working directory, and filesystem root). The arguments idx1 and idx2 are ignored. See the discussion of the CLONE_FS flag in clone(2). KCMP_IO Check whether the processes share I/O context. The arguments idx1 and idx2 are ignored. See the discussion of the CLONE_IO flag in clone(2). KCMP_SIGHAND Check whether the processes share the same table of signal dispositions. The arguments idx1 and idx2 are ignored. See the discus- sion of the CLONE_SIGHAND flag in clone(2). KCMP_SYSVSEM Check whether the processes share the same list of System V semaphore undo operations. The arguments idx1 and idx2 are ignored. See the discussion of the CLONE_SYSVSEM flag in clone(2). KCMP_VM Check whether the processes share the same address space. The arguments idx1 and idx2 are ignored. See the discussion of the CLONE_VM flag in clone(2). KCMP_EPOLL_TFD (since Linux 4.13) Check whether the file descriptor idx1 of the process pid1 is present in the epoll(7) instance described by idx2 of the process pid2. The argument idx2 is a pointer to a structure where the target file is described. This structure has the form: struct kcmp_epoll_slot { __u32 efd; __u32 tfd; __u64 toff; }; Within this structure, efd is an epoll file descriptor returned from epoll_create(2), tfd is a target file descriptor number, and toff is a target file offset counted from zero. Several different targets may be registered with the same file descriptor number and setting a spe- cific offset helps to investigate each of them. Note the kcmp() is not protected against false positives which may occur if the processes are currently running. One should stop the pro- cesses by sending SIGSTOP (see signal(7)) prior to inspection with this system call to obtain meaningful results. RETURN VALUE
The return value of a successful call to kcmp() is simply the result of arithmetic comparison of kernel pointers (when the kernel compares resources, it uses their memory addresses). The easiest way to explain is to consider an example. Suppose that v1 and v2 are the addresses of appropriate resources, then the return value is one of the following: 0 v1 is equal to v2; in other words, the two processes share the resource. 1 v1 is less than v2. 2 v1 is greater than v2. 3 v1 is not equal to v2, but ordering information is unavailable. On error, -1 is returned, and errno is set appropriately. kcmp() was designed to return values suitable for sorting. This is particularly handy if one needs to compare a large number of file descriptors. ERRORS
EBADF type is KCMP_FILE and fd1 or fd2 is not an open file descriptor. EINVAL type is invalid. EPERM Insufficient permission to inspect process resources. The CAP_SYS_PTRACE capability is required to inspect processes that you do not own. Other ptrace limitations may also apply, such as CONFIG_SECURITY_YAMA, which, when /proc/sys/kernel/yama/ptrace_scope is 2, limits kcmp() to child processes; see ptrace(2). ESRCH Process pid1 or pid2 does not exist. EFAULT The epoll slot addressed by idx2 is outside of the user's address space. ENOENT The target file is not present in epoll(7) instance. VERSIONS
The kcmp() system call first appeared in Linux 3.5. CONFORMING TO
kcmp() is Linux-specific and should not be used in programs intended to be portable. NOTES
Glibc does not provide a wrapper for this system call; call it using syscall(2). This system call is available only if the kernel was configured with CONFIG_CHECKPOINT_RESTORE. The main use of the system call is for the checkpoint/restore in user space (CRIU) feature. The alternative to this system call would have been to expose suitable process informa- tion via the proc(5) filesystem; this was deemed to be unsuitable for security reasons. See clone(2) for some background information on the shared resources referred to on this page. EXAMPLE
The program below uses kcmp() to test whether pairs of file descriptors refer to the same open file description. The program tests differ- ent cases for the file descriptor pairs, as described in the program output. An example run of the program is as follows: $ ./a.out Parent PID is 1144 Parent opened file on FD 3 PID of child of fork() is 1145 Compare duplicate FDs from different processes: kcmp(1145, 1144, KCMP_FILE, 3, 3) ==> same Child opened file on FD 4 Compare FDs from distinct open()s in same process: kcmp(1145, 1145, KCMP_FILE, 3, 4) ==> different Child duplicated FD 3 to create FD 5 Compare duplicated FDs in same process: kcmp(1145, 1145, KCMP_FILE, 3, 5) ==> same Program source #define _GNU_SOURCE #include <sys/syscall.h> #include <sys/wait.h> #include <sys/stat.h> #include <stdlib.h> #include <stdio.h> #include <unistd.h> #include <fcntl.h> #include <linux/kcmp.h> #define errExit(msg) do { perror(msg); exit(EXIT_FAILURE); } while (0) static int kcmp(pid_t pid1, pid_t pid2, int type, unsigned long idx1, unsigned long idx2) { return syscall(SYS_kcmp, pid1, pid2, type, idx1, idx2); } static void test_kcmp(char *msg, id_t pid1, pid_t pid2, int fd_a, int fd_b) { printf(" %s ", msg); printf(" kcmp(%ld, %ld, KCMP_FILE, %d, %d) ==> %s ", (long) pid1, (long) pid2, fd_a, fd_b, (kcmp(pid1, pid2, KCMP_FILE, fd_a, fd_b) == 0) ? "same" : "different"); } int main(int argc, char *argv[]) { int fd1, fd2, fd3; char pathname[] = "/tmp/kcmp.test"; fd1 = open(pathname, O_CREAT | O_RDWR, S_IRUSR | S_IWUSR); if (fd1 == -1) errExit("open"); printf("Parent PID is %ld ", (long) getpid()); printf("Parent opened file on FD %d ", fd1); switch (fork()) { case -1: errExit("fork"); case 0: printf("PID of child of fork() is %ld ", (long) getpid()); test_kcmp("Compare duplicate FDs from different processes:", getpid(), getppid(), fd1, fd1); fd2 = open(pathname, O_CREAT | O_RDWR, S_IRUSR | S_IWUSR); if (fd2 == -1) errExit("open"); printf("Child opened file on FD %d ", fd2); test_kcmp("Compare FDs from distinct open()s in same process:", getpid(), getpid(), fd1, fd2); fd3 = dup(fd1); if (fd3 == -1) errExit("dup"); printf("Child duplicated FD %d to create FD %d ", fd1, fd3); test_kcmp("Compare duplicated FDs in same process:", getpid(), getpid(), fd1, fd3); break; default: wait(NULL); } exit(EXIT_SUCCESS); } SEE ALSO
clone(2), unshare(2) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 KCMP(2)
All times are GMT -4. The time now is 01:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy