Thread: CreateProcess

Hi,
Is there something like windows CreateProcess in linux?
The only way to start a process in my program is to use system(); ?
Oh, do not answer to this question please

Any answer is appreciated

Thanks, But As I understood fork() creates a child process with the same memory address.
But I want to start another bin or executable file!!! Run another program?

Yes, But as I know all of this functions invoke a shell to do that?!!!!
Any system call?!

thanks, I got it now

Originally Posted by hosseinyounesi

Yes, But as I know all of this functions invoke a shell to do that?!!!!
Any system call?!

No, the exec family of functions doesn't invoke a shell.

this can be a way. But the forked process name is not the executed application name!!! It's name is the process name that calls fork? Am I right? How to fix this?

Thanks anyone

CreateProcess is the equivalent of a fork() then an exec() of some sort. *nix gives more flexibility in process creation than Windows does.

You are right. Another question: If a child process terminate before the parent, after a few time the parent will be a "Zombie" process. And we know that "exec(newProcess)" family system calls, replace (so the child will terminate) the current process with newProcess.
If I use a fork and If I use exec in child process, the parent will not be a Zombie process! Why?
Thanks in advance

man waitpid:

Originally Posted by man waitpid

WAIT(2) Linux Programmer's Manual WAIT(2)

NAME
wait, waitpid, waitid - wait for process to change state

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

pid_t wait(int *status);

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

int waitid(idtype_t idtype, id_t id, siginfo_t *infop, int options);

Feature Test Macro Requirements for glibc (see feature_test_macros(7)):

waitid(): _SVID_SOURCE || _XOPEN_SOURCE

DESCRIPTION
All of these system calls are used to wait for state changes in a child of the calling process, and obtain information about the
child whose state has changed. A state change is considered to be: the child terminated; the child was stopped by a signal; or the
child was resumed by a signal. In the case of a terminated child, performing a wait allows the system to release the resources
associated with the child; if a wait is not performed, then the terminated child remains in a "zombie" state (see NOTES below).

If a child has already changed state, then these calls return immediately. Otherwise they block until either a child changes state
or a signal handler interrupts the call (assuming that system calls are not automatically restarted using the SA_RESTART flag of
sigaction(2)). In the remainder of this page, a child whose state has changed and which has not yet been waited upon by one of
these system calls is termed waitable.

wait() and waitpid()
The wait() system call suspends execution of the calling process until one of its children terminates. The call wait(&status) is
equivalent to:

waitpid(-1, &status, 0);

Thanks, But my question is: When I use fork and the exec in child process, the parent will not be "zombie" although the child is terminated. WHY ?

(As you know, If a child terminates before parent, the parent will be "zombie")

Thanks