Differences between current version and previous revision of clone(2).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Thursday, October 31, 2002 8:47:44 am | by PerryLorier | |
| Older page: | version 4 | Last edited on Thursday, October 31, 2002 8:45:48 am | by PerryLorier | Revert |
@@ -27,25 +27,21 @@
;__CLONE_PARENT__: (Linux 2.4 onwards) If __CLONE_PARENT__ is set, then the parent of the new child (as returned by getppid(2)) will be the same as that of the calling process.
;:If __CLONE_PARENT__ is not set, then (as with fork(2)) the child's parent is the calling process.
-;:Note that it is the parent process, as returned by getppid(2), which is signaled when the child terminates, so that if __CLONE_PARENT__ is set, then the parent of the calling process, rather than the calling
-
+;:Note that it is the parent process, as returned by getppid(2), which is signaled when the child terminates, so that if __CLONE_PARENT__ is set, then the parent of the calling process, rather than the calling process itself, will be signaled.
-;__CLONE_FS__: If __CLONE_FS__ is set, the caller and the child processes share the same file system information. This includes the root of the file system, the current working directory, and the umask. Any call to chroot(2), chdir(2), or umask(2) performed by the callng process or the child process also takes effect in the other
-
+;__CLONE_FS__: If __CLONE_FS__ is set, the caller and the child processes share the same file system information. This includes the root of the file system, the current working directory, and the umask. Any call to chroot(2), chdir(2), or umask(2) performed by the callng process or the child process also takes effect in the other process.
-;:If __CLONE_FS__ is not set, the child process works on a copy of the file system information of the calling process at the time of the __clone__ call. Calls to
-
+;:If __CLONE_FS__ is not set, the child process works on a copy of the file system information of the calling process at the time of the __clone__ call. Calls to chroot(2), chdir(2), umask(2) performed later by one of the processes do not affect the other process.
;__CLONE_FILES__: If __CLONE_FILES__ is set, the calling process and the child processes share the same file descriptor table. File descriptors always refer to the same files in the calling process and in the child process. Any file descriptor created by the calling process or by the child process is also valid in the other process. Similarly, if one of the processes closes a file descriptor, or changes its associated flags, the other process is also affected.
;:If __CLONE_FILES__ is not set, the child process inherits a copy of all file descriptors opened in the calling process at the time of __clone__. Operations on file descriptors performed later by either the calling process or the child process do not affect the other process.
;__CLONE_SIGHAND__: If __CLONE_SIGHAND__ is set, the calling process and the child processes share the same table of signal handlers. If the calling process or child process calls sigaction(2) to change the behavior associated with a signal, the behavior is changed in the other process as well. However, the calling process and child processes still have distinct signal masks and sets of pending signals. So, one of them may block or unblock some signals using sigprocmask(2) without affecting the other process.
-;:If __CLONE_SIGHAND__ is not set, the child process inherits a copy of the signal handlers of the calling process at the time __clone__ is called. Calls to sigaction(2) performed later by one of the processes
-
+;:If __CLONE_SIGHAND__ is not set, the child process inherits a copy of the signal handlers of the calling process at the time __clone__ is called. Calls to sigaction(2) performed later by one of the processes have no effect on the other process.
;__CLONE_PTRACE__: If __CLONE_PTRACE__ is specified, and the calling process is being traced, then trace the child also (see ptrace(2)).
;__CLONE_VFORK__: If __CLONE_VFORK__ is set, the execution of the calling process is suspended until the child releases its virtual memory resources via a call to execve(2) or _exit(2) (as with vfork(2)).
@@ -63,9 +59,9 @@
;:This flag can only be specified by the system boot process (PID 0).
;__CLONE_THREAD__: (Linux 2.4 onwards) If __CLONE_THREAD__ is set, the child is placed in the same thread group as the calling process.
-;If __CLONE_THREAD__ is not set, then the child is placed in its own (new) thread group, whose ID is the same as the process ID.
+;:
If __CLONE_THREAD__ is not set, then the child is placed in its own (new) thread group, whose ID is the same as the process ID.
;:(Thread groups are feature added in Linux 2.4 to support the POSIX threads notion of a set of threads sharing a single PID. In Linux 2.4, calls to getpid(2) return the thread group ID of the caller.)
The __sys_clone__ system call corresponds more closely to fork(2) in that execution in the child continues from the point of the call. Thus, __sys_clone__ only requires the ''flags'' and ''child_stack'' arguments, which have the same meaning as for __clone__. (Note that the order of these arguments differs from __clone__.)
