From: smccoy@dw3g.ess.harris.com (Cheshire Cat)
Subject: Re: Them 'man' pages
Date: Tue, 12 Jan 1993 22:02:13 GMT
Organization: Harris Corporation Information Systems Division

PuterDude writes:
|>  rip@sequent.com (Paul T Taylor) tugs at my softwear...
                                               ^^^^^^^^
I used to do alot of resume reviewing, interviewing, hiring, etc.
and I once ('struth!) got a resume from a new grad who spelled
software as softwear!  Three times!  It was pretty funny, since 
the cover letter included a graduation picture (!) and concluded 
with a paragraph saying that since the kid was out in Colorado 
skiing, anyone interested in setting up an interview should 
contact his mom!

*snicker*

I figure his mom wrote the resume and cover letter (real proud
of her son, she was).

|> 
|> My favorite...
|> 
|> $ man woman
|> man: woman not found
|> 
|> *sigh* *sniff*
|> 

My favorite:

$ man baby


baby(1)                  USER COMMANDS                    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 ver-
     sion 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 implentations 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 comple-
     tion, 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 m -name Christian Hays Brunton

          completed successfully on July 12,  1992 at 3:04am.  
	  Christian's vital  statistics:  7  pounds 3 oz, 19 
	  inches long dark hair.  The parent process, Laura  
	  Brunton, 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 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.


---
Cheshire Cat		   Official Back Scratcher of the RFA

	Rumour sprendin' a'round in that Texas town
	'bout that shack outside La Grange
	And you know what I'm talkin' about.
		(ZZ Top)
Newsgroups: alt.romance.chat