[SOLVED] Multithreaded tcp server - thread not executing as expected.

which would be fine if the client was on the server.. but if it was on a different machine.. a ctrl c would just kill the client and the tcp stack would issue a FIN... and so changing the code to deal with that wouldn't do jack no?

The SIGPIPE signal is caused by the write(sockfd, "DATA-ACK", strlen("DATA-ACK")); trying to write to a connection the other end has already dropped. Use send(sockfd, "DATA-ACK", strlen("DATA-ACK"), MSG_NOSIGNAL); instead. It will return (ssize_t)-1 with errno set to EPIPE instead of raising the SIGPIPE signal.
Hope this helps,

Nominal Animal

Nominal animal is dead on. Thanks for that, I couldn't think of what to append and change.

nominal animal made me think... yeah catch that error so I tried:

if((write(sockfd, "DATA-ACK", strlen("DATA-ACK"))) == -1) {
	  fprintf(fp, "%s,disconnect\n",inet_ntoa(client_addr.sin_addr));
	  fclose(fp);
	  printf("can't catch SIGPIPE signal\n");
	  printf("Error on read\n");
	  close(sockfd);
	  pthread_exit(NULL);
      }

Which in turn worked, and as the clients disconnect the threads are terminated.. so score!

Thanks guys for the help!! I gotta factor this code now for epoll and then profile all three and compare them - I'll definately be using this forum more. Again, super grateful!

Glad to know that we helped. If your problem is solved, mark the thread as solved and give rep or whatever