You are not logged in.
Pages: 1
I thought this was pretty clever, and I just had to share the fun
BABY(1) BABY(1)
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 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 system load at com-
pletion, and thus current versions of baby expect both parent processes to be active dur-
ing 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 process, 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 pro-
cesses 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 intermittent signals to the parent processes
which must be handled by the parents immediately.
A baby process will frequently dump core, requiring either or both parent processes to
clean up after it.
Despite the reams of available documentation on invoking and maintaining baby, most parent
processes are overwhelmed.
AUTHORS
From a man page by Joe Beck, <beck@cs.ualberta.ca>.
Offline
That's actually pretty good. Now all someone needs to do is come up with a command called "bathwater"
Last edited by gutterslob (2015-03-08 21:43:06)
Point & Squirt
Offline
empty@Debian ~ % man baby
No manual entry for baby
16 empty@Debian ~ % :(
This is in sid -- is the page only in wheezy?
Last edited by Head_on_a_Stick (2015-03-08 21:53:49)
Offline
same error for me too.
wheatly ~ % man baby
No manual entry for baby
wheatly ~ %
occurs in bash too lawl
Last edited by CSCoder4ever (2015-03-08 23:09:06)
Offline
real debian users always install asr-manpages and funny-manpages....just sayin....
install asr-manpages for
https://packages.debian.org/sid/all/asr … s/filelist
install funny-manpages for
https://packages.debian.org/sid/all/fun … s/filelist
Offline
Offline
And I'm not a real debian user soo...
Offline
you can also find them online...
for example - http://manned.org/bosskill.8
I think I seen bug reports mentioning license issues so I suspect they will disappear from debian unless they can be corrected.
As far as not being available in jessie....freeze is the time that it is acceptable to grab things from unstable as for the most part this weeks unstable is next weeks testing...
Last edited by AnInkedSoul (2015-03-09 03:17:40)
Offline
real debian users always install asr-manpages and funny-manpages....just sayin....
install asr-manpages for
https://packages.debian.org/sid/all/asr … s/filelistinstall funny-manpages for
https://packages.debian.org/sid/all/fun … s/filelist
Excellent -- thank you!
Offline
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat