Sponsored Content
Top Forums Programming Linux BSD sockets blocking issue Post 302222157 by johnmb on Wednesday 6th of August 2008 06:19:55 AM
Old 08-06-2008
Linux BSD sockets blocking issue

I am using BSD TCP sockets under Debian Linux 2.6 and no matter what I do, the socket blocks on recv.

I have set O_NONBLOCK and O_NDELAY using fcntl to no effect.

Any ideas ?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

linux + bsd + solaris

I prepare to install linux distros , freebsd and solaris(totally 6 OS) in a 40G harddisk, but I fail to do it, so I would like to ask some question here. Can different distros share the same linux swap?or each distros need to have their own? I made 6 partitions(5 x 7G , 1 x 4G) and 256M(I... (8 Replies)
Discussion started by: jcheng
8 Replies

2. BSD

for linux and BSD users interested in Unix system V/bsd

for all you unix/linux interested heres an online book for free that covers the basics of BSD SysV Unix commands and applications . giving the average linux user a perspective on the differences in context of the two operating systems and for BSD users covers material as a refernce guide. ... (0 Replies)
Discussion started by: moxxx68
0 Replies

3. Programming

C programming on Linux/BSD : which tools to use?

Hello there, i've lurked this forum for a while (in few month i will have been registered for two years) but this is my firts post. Well, after having looked to C language as a black monster, i finally have decided to learn it, and to learn it very well! So, i'm quite new to C, although i... (1 Reply)
Discussion started by: Freddie
1 Replies

4. Cybersecurity

[Linux] Blocking Your w00tw00ts with iptables

I noticed a few w00tw00ts in our Apache2 logfile the other day, so I thought I would write a quick post on blocking them with iptables. Feel free to improve upon any of my scripts or ideas in this thread. First of all, what is a w00tw00t and where might we find one? Well, a w00tw00t is an... (10 Replies)
Discussion started by: Neo
10 Replies

5. UNIX for Dummies Questions & Answers

Partial Write for sockets in LINUX

We have a server-client communication in our application. Sockets are used for the communication. We are using AF_INET sockets with SOCK_STREAM(TCP/IP). Also these sockets are in Non Blocking mode (O_NONBLOCK). Application is written in C++ on UNIX. In our system the Server will write to a... (4 Replies)
Discussion started by: sanushchacko
4 Replies

6. Programming

Sockets (C under Linux)

Hi, I have to write an UDP broadcast. It works so far, but how can I get the actual network address at runtime? Should run under Linux and Unix (Solaris). Thanks (1 Reply)
Discussion started by: peng1967
1 Replies

7. UNIX and Linux Applications

Unix/Linux/BSD

I'm planning to learn Unix/Linux as much as possible to be able to expert on Unix system. I have a few questions in regard to Unix system 1. How come they are so many different type of Linux, and do they follow same standard commands in the Unix system? I'm afraid of having so many choices... (6 Replies)
Discussion started by: mindful123
6 Replies

8. Programming

Which are blocking and non-blocking api's in sockets in C ?

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
RECV(3P)						     POSIX Programmer's Manual							  RECV(3P)

PROLOG
This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the correspond- ing Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. NAME
recv - receive a message from a connected socket SYNOPSIS
#include <sys/socket.h> ssize_t recv(int socket, void *buffer, size_t length, int flags); DESCRIPTION
The recv() function shall receive a message from a connection-mode or connectionless-mode socket. It is normally used with connected sock- ets because it does not permit the application to retrieve the source address of received data. The recv() function takes the following arguments: socket Specifies the socket file descriptor. buffer Points to a buffer where the message should be stored. length Specifies the length in bytes of the buffer pointed to by the buffer argument. flags Specifies the type of message reception. Values of this argument are formed by logically OR'ing zero or more of the following val- ues: MSG_PEEK Peeks at an incoming message. The data is treated as unread and the next recv() or similar function shall still return this data. MSG_OOB Requests out-of-band data. The significance and semantics of out-of-band data are protocol-specific. MSG_WAITALL On SOCK_STREAM sockets this requests that the function block until the full amount of data can be returned. The function may return the smaller amount of data if the socket is a message-based socket, if a signal is caught, if the connection is terminated, if MSG_PEEK was specified, or if an error is pending for the socket. The recv() function shall return the length of the message written to the buffer pointed to by the buffer argument. For message-based sock- ets, such as SOCK_DGRAM and SOCK_SEQPACKET, the entire message shall be read in a single operation. If a message is too long to fit in the supplied buffer, and MSG_PEEK is not set in the flags argument, the excess bytes shall be discarded. For stream-based sockets, such as SOCK_STREAM, message boundaries shall be ignored. In this case, data shall be returned to the user as soon as it becomes available, and no data shall be discarded. If the MSG_WAITALL flag is not set, data shall be returned only up to the end of the first message. If no messages are available at the socket and O_NONBLOCK is not set on the socket's file descriptor, recv() shall block until a message arrives. If no messages are available at the socket and O_NONBLOCK is set on the socket's file descriptor, recv() shall fail and set errno to [EAGAIN] or [EWOULDBLOCK]. RETURN VALUE
Upon successful completion, recv() shall return the length of the message in bytes. If no messages are available to be received and the peer has performed an orderly shutdown, recv() shall return 0. Otherwise, -1 shall be returned and errno set to indicate the error. ERRORS
The recv() function shall fail if: EAGAIN or EWOULDBLOCK The socket's file descriptor is marked O_NONBLOCK and no data is waiting to be received; or MSG_OOB is set and no out-of-band data is available and either the socket's file descriptor is marked O_NONBLOCK or the socket does not support blocking to await out-of- band data. EBADF The socket argument is not a valid file descriptor. ECONNRESET A connection was forcibly closed by a peer. EINTR The recv() function was interrupted by a signal that was caught, before any data was available. EINVAL The MSG_OOB flag is set and no out-of-band data is available. ENOTCONN A receive is attempted on a connection-mode socket that is not connected. ENOTSOCK The socket argument does not refer to a socket. EOPNOTSUPP The specified flags are not supported for this socket type or protocol. ETIMEDOUT The connection timed out during connection establishment, or due to a transmission timeout on active connection. The recv() function may fail if: EIO An I/O error occurred while reading from or writing to the file system. ENOBUFS Insufficient resources were available in the system to perform the operation. ENOMEM Insufficient memory was available to fulfill the request. The following sections are informative. EXAMPLES
None. APPLICATION USAGE
The recv() function is equivalent to recvfrom() with a zero address_len argument, and to read() if no flags are used. The select() and poll() functions can be used to determine when data is available to be received. RATIONALE
None. FUTURE DIRECTIONS
None. SEE ALSO
poll(), read(), recvmsg(), recvfrom(), select(), send(), sendmsg(), sendto(), shutdown(), socket(), write(), the Base Definitions volume of IEEE Std 1003.1-2001, <sys/socket.h> COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 RECV(3P)
All times are GMT -4. The time now is 05:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy