SYNOPSIS
marriage [OPTIONS] [bride] [groom]
DESCRIPTION
marriage (1) is the final version of affiance (1).
Successful completion of marriage (1) results in the creation and nam-
ing of a new shared process. The participating processes then broadcast
messages to all other processes, local and remote, informing them of
their new status.
OPTIONS
-c Creates one, if not several child processes. Equivalent to -s -m
--disable-contract
May result in all of the groom processes priviliges being trans-
ferred to the bride process, should a SIGTERM be recieved.
-h or --help
Request marriage councelling
-m mount significant other
--name Name of the new shared process
-s sleep with significant other
-v or --verbose
Confess the complete truth to significant other
EXAMPLES
marriage --name $NACHNAME $FRAU Schorsch
started successfully on Oct 31, 2007.
ENVIRONMENT VARIABLES
HOME Shared environment where both processes keep all their viable
data. Might occasionally be the location of resource conflicts.
SIGNALS
If the groom process sends a SIGHUP to the bride process this may
result in a SIGKILL coming back.
SIGQUIT can also be sent by a special utility called divorce (1).
WARNINGS
Open tubes of toothpaste and lifted toiled lids will result in an imme-
diate coredump.
With increased runtime of marriage (1) curlers, oily skin cream, beer
cans and tighty whity will be added automatically and can result in
horrible coredumps (and perhaps system crashes) too
ERRORS
If either groom or bride tries to execute sex (1) with other parties
after executing marriage (1), this results in EPERM
BUGS
marriage (1) automatically spawns a daemon called mother-in-law which
is connected through a socket with the bride or groom process respec-
tively.
SEE ALSO
baby(1)
AUTHORS
Marianne Spiller <$EMAIL>
Rainer Jochem <$EMAIL>
Wolfgang Herget <$EMAIL>
Version 42: 07 Nov 2007 MARRIAGE(1)

SYNOPSIS
marriage [OPTIONS] [bride] [groom]
DESCRIPTION
marriage (1) is the final version of affiance (1).
Successful completion of marriage (1) results in the creation and nam-
ing of a new shared process. The participating processes then broadcast
messages to all other processes, local and remote, informing them of
their new status.
OPTIONS
-c Creates one, if not several child processes. Equivalent to -s -m
--disable-contract
May result in all of the groom processes priviliges being trans-
ferred to the bride process, should a SIGTERM be recieved.
-h or --help
Request marriage councelling
-m mount significant other
--name Name of the new shared process
-s sleep with significant other
-v or --verbose
Confess the complete truth to significant other
EXAMPLES
marriage --name $NACHNAME $FRAU Schorsch
started successfully on Oct 31, 2007.
ENVIRONMENT VARIABLES
HOME Shared environment where both processes keep all their viable
data. Might occasionally be the location of resource conflicts.
SIGNALS
If the groom process sends a SIGHUP to the bride process this may
result in a SIGKILL coming back.
SIGQUIT can also be sent by a special utility called divorce (1).
WARNINGS
Open tubes of toothpaste and lifted toiled lids will result in an imme-
diate coredump.
With increased runtime of marriage (1) curlers, oily skin cream, beer
cans and tighty whity will be added automatically and can result in
horrible coredumps (and perhaps system crashes) too
ERRORS
If either groom or bride tries to execute sex (1) with other parties
after executing marriage (1), this results in EPERM
BUGS
marriage (1) automatically spawns a daemon called mother-in-law which
is connected through a socket with the bride or groom process respec-
tively.
SEE ALSO
baby(1)
AUTHORS
Marianne Spiller <$EMAIL>
Rainer Jochem <$EMAIL>
Wolfgang Herget <$EMAIL>
Version 42: 07 Nov 2007 MARRIAGE(1)