mjhjmtu

I searched a lot but didn't find solution. So it can be silly question.

The format of waitpid is

pid_t waitpid (pid_t pid, int *status, int options)

The pid parameter specifies exactly which process or processes to wait for. Its values fall into
four camps:

< -1
Wait for any child process whose process group ID is equal to the absolute value of this value.

-1
Wait for any child process. This is the same behavior as wait( ).

0
Wait for any child process that belongs to the same process group as the calling process. 

> 0
Wait for any child process whose pid is exactly the value provided.

Now the question is what if parent and child have different group id and group id of child is 1. How to use waitpid for this specific child? Because we can't use -1 it will tell to wait for any child.

You can only wait for children from your process.

If the child changes it's process group id, the new process group id can be used as a negative number with waitpid().

BTW: the function waitpid() is deprecated since 1989. The modern function is: waitid() and it supports what you like:

waitid(idtype, id, infop, opts) 
 idtype_t idtype; 
 id_t id; 
 siginfo_t *infop; /* Must be != NULL */ 
 int opts; 

If you like to wait for a process group, use:

waitid(P_PGID, pgid, infop, opts);

So if you really have a process under process group ID 1, call:

waitid(P_PGID, 1, infop, opts);

But since init already uses this process group id, you would need to be the init process in order to able to have children under pgid 1.

This however will not work, if you are on a platform that does not implement waitid() as a syscall but as an emulation on top of the outdated waitpid().

The advantages of waitid() are:

• allows to cleanly specify what to wait for (e.g. P_PID P_PGID P_ALL)




• returns all 32 bits from the exit(2) parameter in the child back to the parent process.




• allows to wait with the flag: WNOWAIT that does not reap the child and keeps it for later in the process table.

BTW: The siginfo_t pointer in waitid() is identical to the second parameter of the signal handler function for SIGCHLD.

You'll have some trouble getting into a situation where the process group ID of a child process is 1.

Process groups are mostly for shells running foreground and background processes (pipelines). Usually, when a new process group is started, it gets the process group id from the first process's process id. You won't get a child with PID 1, so you won't get a child with PGID 1, either.

The setpgid() call allows to move process from one process group to another, but they still need to be part of the same (login) session, so you can't move a process to PGID 1 that way either.

If you have a shell running as PID 1, then it could have PGID 1, too. But as long as the shell changes the PGID of its children, they'll have a different PGID.