Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Feb 2017 22:52:35 +0100
From:      Bernt Hansson <bah@bananmonarki.se>
To:        freebsd-questions@freebsd.org
Subject:   Re: Programmer's Prayer
Message-ID:  <34620197-f8a2-fab2-a6b0-85788bebf505@bananmonarki.se>
In-Reply-To: <CY4PR20MB1397A137DA6C014858313558804A0@CY4PR20MB1397.namprd20.prod.outlook.com>
References:  <CY4PR20MB1397A137DA6C014858313558804A0@CY4PR20MB1397.namprd20.prod.outlook.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 2017-01-31 13:52, Gerard Seibert wrote:
> PROGRAMMER’S PRAYER
>
> Our program, who art in memory,
> called by thy name;
> thy operating system run;
> thy function be done at runtime
> as it was in development.
>
> Give us this day our daily output.
> and forgive us our code duplication,
> as we forgive those who
> duplicate code against us.
>
> And lead us not in frustration,
> but deliver us from GOTOs.
>
> For thine is the algorithm,
> the computation and the solution,
> looping forever and ever.
>
> RETURN
>
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 exe_
cution.

Older implementations of baby did not require both initiating processes
to be present at the time of completion. In those versions the initi_
ating process which was not present was awakened and notified of the
results upon completion. It has since been determined that the pres_
ence of both parent processes result in a generally lower system load
at completion, and thus current versions of baby expect both parent
processes to be active during the final stages.

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 new status.

OPTIONS
-sex define the gender of the created process

-name assign the name name to the new process

EXAMPLES
baby -sex f -name Jacqueline

completed successfully on July 9, 1992 at 9:11pm. Jacqueline's vital
statistics: 8 pounds 3 oz, 20 inches, long dark hair. The parent pro_
cess, Kim Dunbar, is reportedly doing fine.

SEE ALSO
cigar(6), dump(5), cry(3).

BUGS
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 inspect the baby
process to determine the cause of the signal.

The sleep(1) command may not work as expected on either parent process
for some time afterward, as each new instance of baby sends intermit_
tent signals to the parent processes which must be handled by the par_
ents immediately.

A baby process will frequently dump core, requiring either or both par_
ent processes to clean up after it.

Despite the reams of available documentation on invoking and maintain_
ing baby, most parent processes are overwhelmed.

AUTHORS
 From a man page by Joe Beck, .



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?34620197-f8a2-fab2-a6b0-85788bebf505>