Exec - Revision history

Franks: linking first example of fork(), linking process

2006-02-28T05:09:46Z

linking first example of fork(), linking process

← Older revision		Revision as of 22:09, 27 February 2006
Line 1:		Line 1:
	The <code>exec()</code> system call replaces the current process with a completely different process. This is commonly used in shells, servers, and any number of other types of software, where one program hands off execution to a different program.		The <code>exec()</code> system call replaces the current [[process]] with a completely different process. This is commonly used in shells, servers, and any number of other types of software, where one program hands off execution to a different program.

	A common proceedure is to "<code>fork()</code> and <code>exec()</code>". Here, a process will <code>[[fork]]()</code> to create a new "child" process with the same environment and settings as the "parent" (the original process). The child process will then <code>exec</code> the new program and carry on execution.		A common proceedure is to "<code>[[fork]]()</code> and <code>exec()</code>". Here, a process will <code>fork()</code> to create a new "child" process with the same environment and settings as the "parent" (the original process). The child process will then <code>exec</code> the new program and carry on execution.

	Most command line shells use this proceedure for running programs.		Most command line shells use this proceedure for running programs.

Franks at 05:07, 28 February 2006

2006-02-28T05:07:50Z

← Older revision		Revision as of 22:07, 27 February 2006
Line 1:		Line 1:
	The <code>exec()</code> system call replaces the ~~currently~~ process with a completely different process. This is commonly used in shells, servers, and any number of other types of software, where one program hands off execution to a different program.		The <code>exec()</code> system call replaces the current process with a completely different process. This is commonly used in shells, servers, and any number of other types of software, where one program hands off execution to a different program.

	A common proceedure is to "<code>fork()</code> and <code>exec()</code>". Here, a process will <code>[[fork]]()</code> to create a new "child" process with the same environment and settings as the "parent" (the original process). The child process will then <code>exec</code> the new program and carry on execution.		A common proceedure is to "<code>fork()</code> and <code>exec()</code>". Here, a process will <code>[[fork]]()</code> to create a new "child" process with the same environment and settings as the "parent" (the original process). The child process will then <code>exec</code> the new program and carry on execution.

	Most command line shells use this proceedure for running programs.		Most command line shells use this proceedure for running programs.

Hawson at 22:13, 27 February 2006

2006-02-27T22:13:47Z

New page

The <code>exec()</code> system call replaces the currently process with a completely different process. This is commonly used in shells, servers, and any number of other types of software, where one program hands off execution to a different program.

A common proceedure is to "<code>fork()</code> and <code>exec()</code>". Here, a process will <code>[[fork]]()</code> to create a new "child" process with the same environment and settings as the "parent" (the original process). The child process will then <code>exec</code> the new program and carry on execution.

Most command line shells use this proceedure for running programs.