imported>mutante mNo edit summary |
imported>mutante mNo edit summary |
||
| Line 1: | Line 1: | ||
{{funmanpage}} |
|||
=== NAME === |
=== NAME === |
||
baby -- create new process from two parents |
baby -- create new process from two parents |
||
| Line 11: | Line 13: | ||
Older implementations of baby did not require both initiating processes to be present at the time of completion. In those versions the initiating process which was not present was awakened and notified of the results upon completion. It has since been determined that the presence of both parent processes result in a generally lower sys- tem load at completion, and thus current versions of baby expect both parent processes to be active during the final stages. |
Older implementations of baby did not require both initiating processes to be present at the time of completion. In those versions the initiating process which was not present was awakened and notified of the results upon completion. It has since been determined that the presence of both parent processes result in a generally lower sys- tem load at completion, and thus current versions of baby expect both parent processes to be active during the final stages. |
||
[[Category:Manpages]] |
|||
[[Category:Fun]] |
|||
Revision as of 15:13, 13 April 2006
NAME
baby -- create new process from two parents
SYNOPSIS
baby -sex [m|f] [-name name]
DESCRIPTION
baby is initiated when one parent process polls another server process through a socket connection in the BSD version or through pipes in the System V implementation. baby runs at low priority for approximately forty weeks and then terminates with a heavy system load. Most systems require constant monitoring when baby reaches its final stages of execution.
Older implementations of baby did not require both initiating processes to be present at the time of completion. In those versions the initiating process which was not present was awakened and notified of the results upon completion. It has since been determined that the presence of both parent processes result in a generally lower sys- tem load at completion, and thus current versions of baby expect both parent processes to be active during the final stages.