Advertisement
Guest User

Baby manual page

a guest
Feb 22nd, 2018
87
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.19 KB | None | 0 0
  1. NAME
  2. baby β€” create new process from two parents
  3.  
  4. SYNOPSIS
  5. baby -sex [m|f] [-name name]
  6.  
  7. DESCRIPTION
  8. 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 prior‐
  9. ity 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.
  10.  
  11. 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
  12. and notified of the results upon completion. It has since been determined that the presence of both parent processes result in a generally lower system load at completion, and thus current
  13. versions of baby expect both parent processes to be active during the final stages.
  14.  
  15. Successful completion of baby results in the creation and naming of a new process. Parent processes then broadcast messages to all other processes, local and remote, informing them of their
  16. new status.
  17.  
  18. OPTIONS
  19. -sex define the gender of the created process
  20.  
  21. -name assign the name name to the new process
  22.  
  23. EXAMPLES
  24. baby -sex f -name Jacqueline
  25.  
  26. completed successfully on July 9, 1992 at 9:11pm. Jacqueline's vital statistics: 8 pounds 3 oz, 20 inches, long dark hair. The parent process, Kim Dunbar, is reportedly doing fine.
  27.  
  28. SEE ALSO
  29. cigar(6), dump(5), cry(3).
  30.  
  31. BUGS
  32. Despite its complexity, baby only knows one signal, SIGCHLD, (or SIGCLD in the System V implementation), which it uses to contact the parent processes. One or both parent processes must then
  33. inspect the baby process to determine the cause of the signal.
  34.  
  35. The sleep(1) command may not work as expected on either parent process for some time afterward, as each new instance of baby sends intermittent signals to the parent processes which must be
  36. handled by the parents immediately.
  37.  
  38. A baby process will frequently dump core, requiring either or both parent processes to clean up after it.
  39.  
  40. Despite the reams of available documentation on invoking and maintaining baby, most parent processes are overwhelmed.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement