09-07-2010
1. select returns > 0 if there are available sockets
2. FD_ISSET(sock, &writefds) returns true if sock is in the FDSET and the sock descriptor is ready to write. sock is an integer and is one of the sockets you intend to write.
10 More Discussions You Might Find Interesting
1. Programming
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)
Discussion started by: gio
2 Replies
2. Programming
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)
Discussion started by: siegfried
3 Replies
3. IP Networking
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)
Discussion started by: pa.chidhambaram
2 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: chandrutiptur
0 Replies
5. Programming
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)
Discussion started by: cyler
3 Replies
6. Programming
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)
Discussion started by: gendaox
1 Replies
7. IP Networking
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)
Discussion started by: jake24
2 Replies
8. Shell Programming and Scripting
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)
Discussion started by: lupin..the..3rd
2 Replies
9. Programming
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)
Discussion started by: satish@123
7 Replies
10. Programming
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 NETBSD
bio_s_socket
BIO_s_socket(3) OpenSSL BIO_s_socket(3)
NAME
BIO_s_socket, BIO_new_socket - socket BIO
LIBRARY
libcrypto, -lcrypto
SYNOPSIS
#include <openssl/bio.h>
BIO_METHOD *BIO_s_socket(void);
long BIO_set_fd(BIO *b, int fd, long close_flag);
long BIO_get_fd(BIO *b, int *c);
BIO *BIO_new_socket(int sock, int close_flag);
DESCRIPTION
BIO_s_socket() returns the socket BIO method. This is a wrapper round the platform's socket routines.
BIO_read() and BIO_write() read or write the underlying socket. BIO_puts() is supported but BIO_gets() is not.
If the close flag is set then the socket is shut down and closed when the BIO is freed.
BIO_set_fd() sets the socket of BIO b to fd and the close flag to close_flag.
BIO_get_fd() places the socket in c if it is not NULL, it also returns the socket. If c is not NULL it should be of type (int *).
BIO_new_socket() returns a socket BIO using sock and close_flag.
NOTES
Socket BIOs also support any relevant functionality of file descriptor BIOs.
The reason for having separate file descriptor and socket BIOs is that on some platforms sockets are not file descriptors and use distinct
I/O routines, Windows is one such platform. Any code mixing the two will not work on all platforms.
BIO_set_fd() and BIO_get_fd() are macros.
RETURN VALUES
BIO_s_socket() returns the socket BIO method.
BIO_set_fd() always returns 1.
BIO_get_fd() returns the socket or -1 if the BIO has not been initialized.
BIO_new_socket() returns the newly allocated BIO or NULL is an error occurred.
SEE ALSO
TBA
1.0.1i 2009-07-20 BIO_s_socket(3)