TCP multiconnection server

Hi List,
[and thanks in advance for all your effort! Hope not to be off topic
and if so please redirect me]
I've a TCP server with a blocking select awaiting for incoming
connections (on the original fd) and for packets from already
connected hosts (on the newly per-connection generated fds).
Everything works great as long as i ADD new connections, but when I
close ONE of the active connections on the CLIENT side (by closing the
application), I see that on the server the select returns and I
receives a zero bytes long message from the "recv". According to the
man page this is good as it tells the server that a connection was
closed. Upon such event I don't do any particular thing (I just
thought that It's a good idea to close the old client-fd). From this
point on, I don't seem to be listening to any new connection... I
mean, if I open a new client I don't get any reaction from the server.
Why is that?
I can feed you with as much data/code as you need, but basically what
I do is in the following "pseudo"C-code.

....
fd = socket(...)
bind(fd...);
listen(fd...);
while(1)
{
FDZERO(&set)
for(ALL_CONNECTED_CLIENTS) FD_SET(CLIENTFD, &set);
FD_SET(fd, &set)
select(maxfd+1, &set, 0, 0, NULL);
if(FD_ISSET(fd,&set)) accept(fd,...);
else
{
for(ALL_CONNECTED_CLIENTS)
if(IF_ISSET(CLIENTFD[x], &set)) i = recv(CLIENTFD[x],...);
if (i==0) close(CLIENTFD[x]);
}
}

On Jun 3, 7:39 am, InuY4sha <inuy4... RemoveThis @gmail.com> wrote:

> I've a TCP server with a blocking select awaiting for incoming
> connections (on the original fd) and for packets from already
> connected hosts (on the newly per-connection generated fds).
> Everything works great as long as i ADD new connections, but when I
> close ONE of the active connections on the CLIENT side (by closing the
> application), I see that on the server the select returns and I
> receives a zero bytes long message from the "recv". According to the
> man page this is good as it tells the server that a connection was
> closed. Upon such event I don't do any particular thing (I just
> thought that It's a good idea to close the old client-fd). From this
> point on, I don't seem to be listening to any new connection... I
> mean, if I open a new client I don't get any reaction from the server.
> Why is that?
> I can feed you with as much data/code as you need, but basically what
> I do is in the following "pseudo"C-code.
[snip]

There's a bug in code you haven't shown. Most likely, when 'recv'
returns <=0, you probably don't remove the socket from your list of
connected sockets.

DS