How to know whether socket is ready for write.
By default socket is set for write without checking whether it would block or not? If so how do I know my FD is ready for writing.
I have client and server connected.
client write and read from csock.
server write and read from ssock
suppose the server does :
....
close(ssock); //send FIN to client
othertask();
....
READ ERROR
if after the server close() the client does:
...
read(csock,...);
...... (2 Replies)
I am presently refactoring a windows deamon with an eye towards porting it to linux someday.
Presently the application uses a single background thread and asynchronous socket I/O to implement FTP and HTTP clients in a single switch statement (2000 lines and 100 cases just for the switch... (3 Replies)
Hi Friends,
I have written a program which will listener for more than 1000 requests per second from a single socket descriptor and then it will process those requestes. Its taking X amount of time. Now i want to reduce that time. Will I can write multiple threads to receive the... (2 Replies)
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Why does this socket function only read the first 1440 chars of the stream. Why not the whole stream ? I checked it with gdm and valgrind and everything seems correct...
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <string.h>
#include... (3 Replies)
Can anyone tell what happens if each end writes at the same time on the same socket ?
- if one of them issues a read() after write() has completed, will it record into the buffer what the other sent ?
ex.
e1 writes to e2 - - - while - - - e2 writes to e1 (at the same time)
e1 read () - what... (1 Reply)
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Hello all,
I have a requirement to read and write to a tcp socket from an HP-UX shell script. I see a /dev/tcp character device on my servers:
crw-rw-rw- 1 root root 72 0x00004f Mar 28 18:37 /dev/tcp
So I believe this is what I should use. The problem is that all the... (2 Replies)
will there be any unexpected results on looping connect call for a non blocking socket to determine the connection based on error code. I am getting connection unsuccessful intermittently and so wondering whether is the timeout 500 millisec not sufficient or looping connect cause any unexpected.
... (7 Replies)
among the below socket programming api's, please let me know which are blocking and non-blocking.
socket
accept
bind
listen
write
read
close (2 Replies)
Discussion started by: VSSajjan
2 Replies
LEARN ABOUT DEBIAN
explain_select_or_die
explain_select_or_die(3) Library Functions Manual explain_select_or_die(3)NAME
explain_select_or_die - blah blah and report errors
SYNOPSIS
#include <libexplain/select.h>
void explain_select_or_die(int nfds, fd_set *readfds, fd_set *writefds, fd_set *exceptfds, struct timeval *timeout);
DESCRIPTION
The explain_select_or_die function is used to call the select(2) system call. On failure an explanation will be printed to stderr,
obtained from explain_select(3), and then the process terminates by calling exit(EXIT_FAILURE).
This function is intended to be used in a fashion similar to the following example:
explain_select_or_die(nfds, readfds, writefds, exceptfds, timeout);
nfds The nfds, exactly as to be passed to the select(2) system call.
readfds The readfds, exactly as to be passed to the select(2) system call.
writefds
The writefds, exactly as to be passed to the select(2) system call.
exceptfds
The exceptfds, exactly as to be passed to the select(2) system call.
timeout The timeout, exactly as to be passed to the select(2) system call.
Returns:
This function only returns on success. On failure, prints an explanation and exits.
SEE ALSO select(2)
blah blah
explain_select(3)
explain select(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2008 Peter Miller
explain_select_or_die(3)