Annotated edit history of
socketcall(2) version 3, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
IPC |
| |
|
2 |
!!!IPC |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
CONFORMING TO |
| |
|
7 |
SEE ALSO |
| |
|
8 |
---- |
| |
|
9 |
!!NAME |
| |
|
10 |
|
| |
|
11 |
|
| |
|
12 |
socketcall - socket system calls |
| |
|
13 |
!!SYNOPSIS |
| |
|
14 |
|
| |
|
15 |
|
| 3 |
perry |
16 |
__int socketcall(int__ ''call,'' __unsigned long |
| |
|
17 |
*__''args);'' |
| 1 |
perry |
18 |
!!DESCRIPTION |
| |
|
19 |
|
| |
|
20 |
|
| |
|
21 |
__socketcall__ is a common kernel entry point for the |
| |
|
22 |
socket system calls. ''call'' determines which socket |
| |
|
23 |
function to invoke. ''args'' points to a block containing |
| |
|
24 |
the actual arguments, which are passed through to the |
| |
|
25 |
appropriate call. |
| |
|
26 |
|
| |
|
27 |
|
| |
|
28 |
User programs should call the appropriate functions by their |
| |
|
29 |
usual names. Only standard library implementors and kernel |
| |
|
30 |
hackers need to know about __socketcall__. |
| |
|
31 |
!!CONFORMING TO |
| |
|
32 |
|
| |
|
33 |
|
| |
|
34 |
This call is specific to Linux, and should not be used in |
| |
|
35 |
programs intended to be portable. |
| |
|
36 |
!!SEE ALSO |
| |
|
37 |
|
| |
|
38 |
|
| |
|
39 |
accept(2), bind(2), connect(2), |
| |
|
40 |
getpeername(2), getsockname(2), |
| |
|
41 |
getsockopt(2), listen(2), recv(2), |
| |
|
42 |
recvfrom(2), send(2), sendto(2), |
| |
|
43 |
setsockopt(2), shutdown(2), socket(2), |
| |
|
44 |
socketpair(2) |
| |
|
45 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
