Path: utzoo!news-server.csri.toronto.edu!rpi!usc!samsung!noose.ecn.purdue.edu!ei.ecn.purdue.edu!irick
From: irick@ei.ecn.purdue.edu (GarBear Irick)
Newsgroups: comp.unix.questions
Subject: <defunct> processes
Message-ID: <1991Mar18.065648.16992@noose.ecn.purdue.edu>
Date: 18 Mar 91 06:56:48 GMT
Sender: root@noose.ecn.purdue.edu (ECN System Management)
Distribution: usa
Organization: Purdue Society for Better Computing
Lines: 21

OK, OK, here goes a really stupid question...

In a bit of server code I am working on, I decided that I would allow
multiple clients to connect to the server, meaning a fork() each time a
connection is established.  The child does its job, but when it finishes,
it hangs around as a <defunct> process after the exit().  I am using a
socket, adn the final code goes somethin' like this:

  write(sock,"Bye!\n",5);
  close(sock);
  exit(0);

I thought that maybe signal(SIGCHLD,SIGIGN) would fix it, but alas.  I
never thought I would post such a DUMB question to the net...  please drop
me a line at the address below, since I don't have much time to read news
this week!  Thanks...

--
Gary A. Irick,  Purdue University | "You can log out any time you like,
INTERNET: irick@ei.ecn.purdue.edu |  But you can never leave!"
UUCP:     ...!pur-ee!irick        |       (apologies to The Eagles)