Sponsored Content
Top Forums UNIX for Advanced & Expert Users Doubt with fork() system call Post 302577620 by badsha6642 on Tuesday 29th of November 2011 01:13:32 PM
Old 11-29-2011
Doubt with fork() system call

Hi
I wrote a simple fork program to illustrate the fork() system cal. here it is
Code:
#include<stdio.h>
#include<sys/stat.h>
#include<sys/types.h>
main()
{
    int flag;
    flag=fork();
    if(flag==0)
    {
        printf("Child \n");    
        printf("Process id= %d\n",getpid());
        printf("Parent id= %d\n",getppid());
    }
    if(flag==-1)
        printf("Error!!!");
    else
    {
        printf("Parent\n");
        printf("Process id= %d\n",getpid());
        printf("Parent id= %d\n",getppid());
        printf("value of flag=%d\n",flag);
    }
}

i got the following output
Code:
Parent
Process id= 2332
Parent id= 1855
value of flag=2333
Child 
Process id= 2333
Parent id= 1
Parent
Process id= 2333
Parent id= 1
value of flag=0

i understood the first part i.e parent part,but how the parent id of child becomes 1?? and again how the parent process is called??

Moderator's Comments:
Mod Comment Please use code tags!

Last edited by vbe; 11-29-2011 at 02:19 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

URGENT Help required regarding the use of FORK system call

I desperately wanted one of the UNIX Gurus to help me resolve my problem asap(I have to deliver the code to the client by Monday 08-oct). I have a file with around 5 million records (50 lakhs). Now my original process was taking around 30 hours to read the complete file, process each and every... (4 Replies)
Discussion started by: kkumar1975
4 Replies

2. Programming

Fork() system call time?

One more question. How can i calculate the time that system needs to make fork() system call? I need to make it with times function but i really don't know how. :( (2 Replies)
Discussion started by: davidoff
2 Replies

3. UNIX for Dummies Questions & Answers

fork() system call

Can anyone explain me what really happens when a system call fork() is called ? I like to know what happens internally. Thanks in Advance. - Arun (1 Reply)
Discussion started by: arunviswanath
1 Replies

4. UNIX for Dummies Questions & Answers

fork system call

Hi folks, I want to know how this below program works? #include <stdio.h> int main() { printf("A\n"); fork(); printf("B\n"); fork(); fork(); printf("D\n"); fork(); printf("C\n"); } This is just for example. How this type of programs where fork is used many places, how the... (1 Reply)
Discussion started by: u_peerless
1 Replies

5. Shell Programming and Scripting

Function call with argument doubt

Hi all, I am having a problem with user defined function call. I am new into the concept of shell script UDFs. My function is: iterate_directory() { cd $1 k=0 for i in * do if then ARR=${i} fi done echo ${ARR } } (4 Replies)
Discussion started by: canishk
4 Replies

6. Homework & Coursework Questions

fork system call understanding

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: i have a problem in understanding the behaviour of fork . i understood fork as to create a new process and... (4 Replies)
Discussion started by: MrUser
4 Replies

7. Shell Programming and Scripting

fork system call and \n

hi, i tried the following source codes: fork1.c: main() { printf("demo of fork\n"); fork(); printf("hello"); } output: demo of fork hello hello fork2.c: main() { printf("demo of fork"); (0 Replies)
Discussion started by: pnirmala
0 Replies

8. Programming

Problem with execution of fork system call if i use \n

hi all, i tried the following source codes: fork1.c: main() { printf("demo of fork\n"); fork(); printf("hello"); } output: demo of fork hello hello fork2.c: main() (3 Replies)
Discussion started by: pnirmala
3 Replies

9. Shell Programming and Scripting

Help: how to call fork() in shell script? New to linux

Hi, I'm writing a shell script where I want to call fork(). However I wrote like this "var=fork()" in c style and got this error: "syntax error near unexpected token `(' " How could I call fork() in shell script? Thanks in advance. Duplicate Post - Continue Here - Please Do Not Cross Post... (0 Replies)
Discussion started by: Xiaoya
0 Replies

10. Ubuntu

Help: how to call fork() in shell script? New to linux

Hi, I'm writing a shell script where I want to call fork(). However I wrote like this "var=fork()" in c style and got this error: "syntax error near unexpected token `(' " How could I call fork() in shell script? Thanks in advance. (2 Replies)
Discussion started by: Xiaoya
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 09:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy