Sponsored Content
Top Forums Programming recv syscall for socket programming Post 302205744 by sriprasads on Monday 16th of June 2008 07:24:17 AM
Old 06-16-2008
Thanks, that make sense

hi,

i'm facing the same problem too,
i know the reason, but struggling to solve it.

i found there is a socket type which will recv, packets exactly in the same order sent, without reading the whole junk from buffer...

if u know a way, kindly post....

Thnx,
sri
 

10 More Discussions You Might Find Interesting

1. IP Networking

TCP Programming problems with 'recv'

Hey, I am learning to program a TCP server and managed to get it up and running (I am using Windows 98SE). I can use the send function to send information to the client and I can use the recv function to ask the user to pass information through, but when I do so it only allows the client to... (1 Reply)
Discussion started by: KrazyGuyPaul
1 Replies

2. Programming

Socket Programming socket

Hello, I actually try to make client-server program. I'm using SCO OpenServer Release 5.0.0 and when I try to compile my code (by TELNET) I've got this error : I'm just using this simple code : and I get the same error if I use : If someone can help me, Thanks (2 Replies)
Discussion started by: soshell
2 Replies

3. IP Networking

socket programming

my system is a stand alone system... i want to try doing socket porgramming..ihave heard that this is usually done during testing... how can i do that....? (6 Replies)
Discussion started by: damn_bkb
6 Replies

4. Programming

Socket Programming

Hi , I'm facing the following problem in socket programming. My structure is struct { int i; char *str; }samp; I'm creating the pointer to this structure and assigning the value to the structure members and send via the socket to the another process. The receiver process when... (7 Replies)
Discussion started by: arunviswanath
7 Replies

5. Programming

UDP socket - can both client and server recv and send

Hi, Am very new to socket programming. When we use UDP sockets to communicate between two processess, will both the client/server socket be able to send/recv ? meaning can sendto()/ recvfrom() be used on both server and client? It could be useful even if anybody provide some link on socket... (1 Reply)
Discussion started by: rvan
1 Replies

6. Programming

C Network Programming - recv() help

So I'm making a program that gets the IP Address of an inputed website, then sends the IP Address to an inputed host. This program has no real meaning, but just a learning experiment. So I sucessfully made the program, then I wanted to try out recv(), and it produces some weird output; here is the... (2 Replies)
Discussion started by: Octal
2 Replies

7. IP Networking

socket programming

Hello Everyone Iam working on tcp/ip programming.with some time interval server has to send data.client has to close the connection and to open the connection between the time interval.this is the scenario when iam closing the connection in client side the connection terminates.how to... (1 Reply)
Discussion started by: sureshvaikuntam
1 Replies

8. Programming

Socket programming in C

Hi, I wanted to write a socket program in C, where I always want my socket connected to the server. i.e i shouldn't get disconnected once i get the response back from the server. I want to work in the connected mode, instead of disconnect and connect. Can somebody please kindly provide me a... (3 Replies)
Discussion started by: sudharma
3 Replies

9. UNIX for Advanced & Expert Users

Socket programming

my socket program is not working with larger port numbers like more than 60000 , any reason why ? (4 Replies)
Discussion started by: Gopi Krishna P
4 Replies

10. Programming

Download file with socket syscall

Hello to all I want download a file in osx intel 64 with NASM , I want to use socket syscall This is part of my code section .data command db "GET /test/2.gif HTTP/1.1\r\nHost: 10.1.1.187\r\n\r\n", 0 ; url db "http://172.16.207.153/test/2.gif", 0 global main... (1 Reply)
Discussion started by: recher.jack
1 Replies
recv(2) 							System Calls Manual							   recv(2)

NAME
recv - Receives messages from connected sockets SYNOPSIS
#include <sys/socket.h> ssize_t recv ( int socket, void *buffer, size_t length, int flags ); [Tru64 UNIX] The following definition of the recv() function does not conform to current standards and is supported only for backward com- patibility (see standards(5)): #include <sys/socket.h> int recv ( int socket, char *buffer, int length, int flags ); STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: recv(): XNS5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. PARAMETERS
Specifies the socket descriptor. Points to a buffer where the message should be placed. Specifies the size of the buffer pointed to by the buffer parameter. Points to a value controlling the message reception. The flags parameter is formed by logically ORing one or more of the following values, defined in the sys/socket.h file: Peek at incoming message. The data is treated as unread and the next recv() function (or similar function) will still return this data. Process out-of-band data. Requests that the function block wait until the full amount of data requested can be returned. The function may return a smaller amount of data if a signal is caught, the connection is terminated, or an error is pending for the socket. DESCRIPTION
The recv() function receives messages from a connected socket. The recvfrom() and recvmsg() functions receive messages from both connected and unconnected sockets; however, they are usually used for unconnected sockets only. The recv() function returns the length of the message. If a message is too long to fit in the supplied buffer, excess bytes may be trun- cated depending on the type of socket that issued the message. If no messages are available at the socket, the recv() function waits for a message to arrive, unless the socket is nonblocking. If a socket is nonblocking, errno is set to [EWOULDBLOCK]. Use the select() function to determine when more data arrives. NOTES
[Tru64 UNIX] The recv() function is identical to the recvfrom() function with a zero-valued address_len parameter, and to the read() func- tion if no flags are used. For that reason the recv() function is disabled when 4.4BSD behavior is enabled; that is, when the _SOCK- ADDR_LEN compile-time option is defined. RETURN VALUES
Upon successful completion, the recv() function returns the length of the message in bytes. If no messages are available and the peer has closed the connection, the recv() function returns a value of 0. Otherwise, the function returns a value of -1 and sets errno to indicate the error. ERRORS
If the recv() function fails, errno may be set to one of the following values: The socket parameter is not valid. A connection was forcibly closed by a peer. The data was directed to be received into a nonexistent or protected part of the process address space. The buffer parameter is invalid. A signal interrupted the recv() function before any data was available. The MSG_OOB flag is set and no out- of-band data is available. An I/O error occurred while reading from or writing to the file system. Insufficient resources were available in the system to complete the call. The system did not have sufficient memory to fulfill the request. The available STREAMS resources were insufficient for the operation to complete. Receive is attempted on a connection-oriented socket that is not connected. The socket parameter refers to a file, not a socket. The specified flags are not supported for this socket type or protocol. The connection timed out during connection establishment or due to a transmission timeout on active connection. The socket is marked nonblocking, and no data is waiting to be received. RELATED INFORMATION
Functions: recvfrom(2), recvmsg(2), send(2), sendmsg(2), sendto(2), select(2), shutdown(2), socket(2), read(2), write(2) Standards: standards(5) delim off recv(2)
All times are GMT -4. The time now is 04:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy