Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

getpeername(1) [xfree86 man page]

GETPEERNAME(1)						      General Commands Manual						    GETPEERNAME(1)

NAME
getpeername - get name of connected TCP/IP peer SYNOPSIS
getpeername [-n] [-p protocol] DESCRIPTION
getpeername prints the IP address and service name (port number) of the remote peer connected to standard input. The IP address and the service name are printed on the same line, separated by one space. OPTIONS
-n Don't translate IP addresses and port numbers to names. -p protocol Force getpeername to use protocol as the protocol when translating port numbers to service names. Protocol can be tcp and udp. Normally, getpeername automatically determines what type of socket it is connected to. SEE ALSO
getpeername(3). BUGS
Only works on IP sockets. 1997 April 13 GETPEERNAME(1)

Check Out this Related Man Page

GETPEERNAME(2)						     Linux Programmer's Manual						    GETPEERNAME(2)

NAME
getpeername - get name of connected peer socket SYNOPSIS
#include <sys/socket.h> int getpeername(int s, struct sockaddr *name, socklen_t *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. RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately. ERRORS
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. CONFORMING TO
SVr4, 4.4BSD (the getpeername function call first appeared in 4.2BSD). NOTE
The third argument of getpeername is in reality an `int *' (and this is what BSD 4.* and libc4 and libc5 have). Some POSIX confusion resulted in the present socklen_t. The draft standard has not been adopted yet, but glibc2 already follows it and also has socklen_t. See also accept(2). SEE ALSO
accept(2), bind(2), getsockname(2) BSD Man Page 1993-07-30 GETPEERNAME(2)
Man Page