BIO_s_socket(3) OpenSSL BIO_s_socket(3)NAME
BIO_s_socket, BIO_new_socket - socket BIO
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
50 2013-03-05 BIO_s_socket(3)
Check Out this Related Man Page
BIO_s_socket(3) OpenSSL BIO_s_socket(3)NAME
BIO_s_socket, BIO_new_socket - socket BIO
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
50 2013-03-05 BIO_s_socket(3)
I want to know what are the design considerations to be taken into account. when porting a socket project from Unix platform to another ...... (10 Replies)
Is there any way to get the file descriptor statistics of a socket file descriptor? I know that the fstat, stat system calls are for this purpose, but I want to know it there any way to get socket connection statistics for a file descriptor(like socket flags, connection type etc).
Does /proc... (3 Replies)
I have written a socker program. I have executed that program many times without closing the socket. So I want to find which all sockets binded with which file descriptor.
Is there any way to close those socket, which have been opened in that program's execution.
please help me!.. (3 Replies)
Interesting issue. There was some discussion on the LKML last year regarding the potential problems in concurrent applications reusing file descriptors in various scenarios. The main issue is that the reuse of a file descriptor and reception of data in a threaded application can be confused pretty... (1 Reply)
I have a query related to the functioning of poll() system call on solaris and linux platforms.
When the client is abnormally terminated, it is observed that on Linux the socket is immediately closed and the server gets ECONNREFUSED.
But in case of Solaris it is observed that the socket is not... (0 Replies)
Hello community,
I'm programming a simple code using socket connection in perl:
$sock = new IO::Socket::INET(
PeerAddr => '192.168.10.7',
PeerPort => 8000,
Proto => 'tcp');
$sock or die "no socket :$!";Then sending data using a loop:
... (1 Reply)