Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

getpeername(2) [freebsd man page]

GETPEERNAME(2)						      BSD System Calls Manual						    GETPEERNAME(2)

NAME
getpeername -- get name of connected peer LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/types.h> #include <sys/socket.h> int getpeername(int s, struct sockaddr * restrict name, socklen_t * restrict namelen); DESCRIPTION
The getpeername() system call returns the name of the peer connected to socket s. The namelen argument should be initialized to indicate the amount of space pointed to by name. On return it contains the actual size of the name returned (in bytes). The name is truncated if the buffer provided is too small. RETURN VALUES
The getpeername() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate the error. ERRORS
The call succeeds unless: [EBADF] The argument s is not a valid descriptor. [ECONNRESET] The connection has been reset by the peer. [EINVAL] The value of the namelen argument is not valid. [ENOTSOCK] The argument s is a file, not a socket. [ENOTCONN] The socket is not connected. [ENOBUFS] Insufficient resources were available in the system to perform the operation. [EFAULT] The name argument points to memory not in a valid part of the process address space. SEE ALSO
accept(2), bind(2), getsockname(2), socket(2) HISTORY
The getpeername() system call appeared in 4.2BSD. BSD
June 4, 1993 BSD

Check Out this Related Man Page

GETPEERNAME(2)							System Calls Manual						    GETPEERNAME(2)

NAME
getpeername - get name of connected peer SYNOPSIS
getpeername(s, name, namelen) int s; struct sockaddr *name; int *namelen; DESCRIPTION
Getpeername returns the name of the peer connected to socket s. The namelen parameter should be initialized to indicate the amount of space pointed to by name. On return it contains the actual size of the name returned (in bytes). The name is truncated if the buffer pro- vided is too small. DIAGNOSTICS
A 0 is returned if the call succeeds, -1 if it fails. ERRORS
The call succeeds unless: [EBADF] The argument s is not a valid descriptor. [ENOTSOCK] The argument s is a file, not a socket. [ENOTCONN] The socket is not connected. [ENOBUFS] Insufficient resources were available in the system to perform the operation. [EFAULT] The name parameter points to memory not in a valid part of the process address space. SEE ALSO
accept(2), bind(2), socket(2), getsockname(2) 4.2 Berkeley Distribution May 13, 1986 GETPEERNAME(2)
Man Page

5 More Discussions You Might Find Interesting

1. Programming

advanced socket programming

hi every one my post is about socket programming i would know if anyone knows about send binary file in peer to peer connection. if you have any information about it plzzz contact me or reply my post thx SpY974 (2 Replies)
Discussion started by: SpY974
2 Replies

2. Programming

Anyone know how to use socket select() function?

hello socket programming expert, I having difficulties in understanding how select() function in socket programming work.... I'm trying to create my own peer-to-peer chat or file transfer program by using the select() function.... Therefore does anyone had any tutorial or source code that... (4 Replies)
Discussion started by: draggy
4 Replies

3. UNIX for Dummies Questions & Answers

fatal: Read from socket failed: Connection reset by peer

I get this error when I log in through console: "fatal: Read from socket failed: Connection reset by peer". Can you tell me what this is and why it happens, and how to stop it? Thank you. (1 Reply)
Discussion started by: iamnew2solaris
1 Replies

4. IP Networking

Execution Problem with socket

Hi My socket program is to communicate between the two systems connected with lan. Always i am getting an error saying bind value is -1 or not connected. ..If i run both the server and client programs in the same machine in two diff terminals they are working but they are not working between two... (3 Replies)
Discussion started by: Gurvareddy
3 Replies

5. Solaris

getpeername: Transport endpoint is not connected

Hi Folks, I am getting the following error in /var/adm/messages. Can any one help me out on this? ZXXXXXA:/# tail /var/adm/messages Oct 26 00:13:04 ZXXXXXA ftpd: setsockopt SO_KEEPALIVE Invalid argument Oct 26 00:13:04 ZXXXXXA ftpd: setsockopt (SO_OOBINLINE): Invalid argument Oct 26... (3 Replies)
Discussion started by: vivek.goel.piet
3 Replies