Sponsored Content
Top Forums Programming Linux BSD sockets blocking issue Post 302222179 by jim mcnamara on Wednesday 6th of August 2008 07:09:46 AM
Old 08-06-2008
Have you tried select() with timeout set to non-NULL?

Without your code, this amounts to a wild guess.....
 

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
SEND(2) 						     Linux Programmer's Manual							   SEND(2)

NAME
send, sendto, sendmsg - send a message from a socket SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> int send(int s, const void *msg, size_t len, int flags); int sendto(int s, const void *msg, size_t len, int flags, const struct sockaddr *to, socklen_t tolen); int sendmsg(int s, const struct msghdr *msg, int flags); DESCRIPTION
Send, sendto, and sendmsg are used to transmit a message to another socket. Send may be used only when the socket is in a connected state, while sendto and sendmsg may be used at any time. The address of the target is given by to with tolen specifying its size. The length of the message is given by len. If the message is too long to pass atomically through the underlying protocol, the error EMSGSIZE is returned, and the message is not transmitted. No indication of failure to deliver is implicit in a send. Locally detected errors are indicated by a return value of -1. When the message does not fit into the send buffer of the socket, send normally blocks, unless the socket has been placed in non-blocking I/O mode. In non-blocking mode it would return EAGAIN in this case. The select(2) call may be used to determine when it is possible to send more data. The flags parameter is a flagword and can contain the following flags: MSG_OOB Sends out-of-band data on sockets that support this notion (e.g. SOCK_STREAM); the underlying protocol must also support out-of- band data. MSG_DONTROUTE Dont't use a gateway to send out the packet, only send to hosts on directly connected networks. This is usually used only by diag- nostic or routing programs. This is only defined for protocol families that route; packet sockets don't. MSG_DONTWAIT Enables non-blocking operation; if the operation would block, EAGAIN is returned (this can also be enabled using the O_NONBLOCK with the F_SETFL fcntl(2)). MSG_NOSIGNAL Requests not to send SIGPIPE on errors on stream oriented sockets when the other end breaks the connection. The EPIPE error is still returned. MSG_CONFIRM (Linux 2.3+ only) Tell the link layer that forward process happened: you got a successful reply from the other side. If the link layer doesn't get this it'll regularly reprobe the neighbour (e.g. via a unicast ARP). Only valid on SOCK_DGRAM and SOCK_RAW sockets and currently only implemented for IPv4 and IPv6. See arp(7) for details. The definition of the msghdr structure follows. See recv(2) and below for an exact description of its fields. struct msghdr { void * msg_name; /* optional address */ socklen_t msg_namelen; /* size of address */ struct iovec * msg_iov; /* scatter/gather array */ size_t msg_iovlen; /* # elements in msg_iov */ void * msg_control; /* ancillary data, see below */ socklen_t msg_controllen; /* ancillary data buffer len */ int msg_flags; /* flags on received message */ }; You may send control information using the msg_control and msg_controllen members. The maximum control buffer length the kernel can process is limited per socket by the net.core.optmem_max sysctl; see socket(7). RETURN VALUE
The calls return the number of characters sent, or -1 if an error occurred. ERRORS
These are some standard errors generated by the socket layer. Additional errors may be generated and returned from the underlying protocol modules; see their respective manual pages. EBADF An invalid descriptor was specified. ENOTSOCK The argument s is not a socket. EFAULT An invalid user space address was specified for a parameter. EMSGSIZE The socket requires that message be sent atomically, and the size of the message to be sent made this impossible. EAGAIN or EWOULDBLOCK The socket is marked non-blocking and the requested operation would block. ENOBUFS The output queue for a network interface was full. This generally indicates that the interface has stopped sending, but may be caused by transient congestion. (This cannot occur in Linux, packets are just silently dropped when a device queue overflows.) EINTR A signal occurred. ENOMEM No memory available. EINVAL Invalid argument passed. EPIPE The local end has been shut down on a connection oriented socket. In this case the process will also receive a SIGPIPE unless MSG_NOSIGNAL is set. CONFORMING TO
4.4BSD, SVr4, POSIX 1003.1g draft (these function calls appeared in 4.2BSD). MSG_CONFIRM is a Linux extension. NOTE
The prototypes given above follow the Single Unix Specification, as glibc2 also does; the flags argument was `int' in BSD 4.*, but `unsigned int' in libc4 and libc5; the len argument was `int' in BSD 4.* and libc4, but `size_t' in libc5; the tolen argument was `int' in BSD 4.* and libc4 and libc5. See also accept(2). SEE ALSO
fcntl(2), recv(2), select(2), getsockopt(2), sendfile(2), socket(2), write(2), socket(7), ip(7), tcp(7), udp(7) Linux Man Page 1999-07 SEND(2)
All times are GMT -4. The time now is 04:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy