ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi
iīm experiencing some client/server application programming with C. my idea is to be able to share files between client/server, but there is a problem i couldnīt solve for quiet some time.
i am trying to implement a connection timeout while receiving files.. the idea is that if i am receiving a file from the server suppose, and the server goes down, after X amount of seconds the client (which was receiving the file) should timeout.
what happends is the following. i initiate the transfer of a big file. while transfer is going on, y temrinate the server... but the select function instead of making timeout as i expected, it just kept "rceiving" data, and it never timed out... any ideas?
You should also FD_ZERO after every cycle. Lastly, you need to shutdown sockets when one end exits. Merely closing the descriptor or letting the program exit leaves the socket extant, so the other end doesn't see that the other end is permanently closed until shutdown occurs or the kernel realizes that nothing else can write to the socket.
ta0kira
PS You can replace the while (... && errno == EINTR) with TEMP_FAILURE_RETRY(...).
PPS You also need to re-init the timeout value at the beginning of each cycle since it might be modified as a result of select returning early.
Long ago that I programmed something like that, but if I remember correctly:
When the other side hangs up, select will indicate that the socket is readable and you have to read it. When you read it, you will get zero bytes, which indicates that the other side closed the connection and you can close the socket.
You do read, but you don't check for zero bytes (only less than zero).
Last edited by Wim Sturkenboom; 05-02-2008 at 02:24 PM.
When the other side hangs up, select will indicate that the socket is readable and you have to read it. When you read it, you will get zero bytes, which indicates that the other side closed the connection and you can close the socket.
You do read, but you don't check for zero bytes (only less than zero).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.