Oracle Solaris 11网络库函数第3节：详细文档与指南

oracle

需积分: 5 46 浏览量更新于2024-06-25 收藏 3.1MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

there is no BUGS section. See the intro pages for more information and detail about each

section, and

man(1) for more information about man pages in general.

NAME This section gives the names of the commands or functions

documented, followed by a brief description of what they

do.

SYNOPSIS This section shows the syntax of commands or functions.

When a command or le does not exist in the standard

path, its full path name is shown. Options and arguments

are alphabetized, with single letter arguments rst, and

options with arguments next, unless a dierent argument

order is required.

The following special characters are used in this section:

[ ] Brackets. The option or argument enclosed in

these brackets is optional. If the brackets are

omitted, the argument must be specied.

. . . Ellipses. Several values can be provided for the

previous argument, or the previous argument

can be specied multiple times, for example,

“filename ...”.

| Separator. Only one of the arguments

separated by this character can be specied at a

time.

{ } Braces. The options and/or arguments

enclosed within braces are interdependent,

such that everything enclosed must be treated

as a unit.

PROTOCOL This section occurs only in subsection 3R to indicate the

protocol description le.

DESCRIPTION This section denes the functionality and behavior of the

service. Thus it describes concisely what the command

does. It does not discuss OPTIONS or cite EXAMPLES.

Interactive commands, subcommands, requests, macros,

and functions are described under USAGE.

IOCTL This section appears on pages in Section 7 only. Only the

device class that supplies appropriate parameters to the

ioctl(2) system call is called ioctl and generates its own

heading. ioctl calls for a specic device are listed

alphabetically (on the man page for that specic device).

Preface

man pages section 3: Networking Library Functions • November 201116

accept – accept a connection on a socket

cc [ ag ... ] le ... -lsocket -lnsl [ library ... ]

#include <sys/socket.h>

int accept(int s, struct sockaddr *addr, socklen_t *addrlen);

The argument s is a socket that has been created with socket(3SOCKET) and bound to an

address with bind(3SOCKET), and that is listening for connections after a call to

listen(3SOCKET). The accept() function extracts the rst connection on the queue of

pending connections, creates a new socket with the properties of s, and allocates a new le

descriptor, ns, for the socket. If no pending connections are present on the queue and the

socket is not marked as non-blocking, accept() blocks the caller until a connection is present.

If the socket is marked as non-blocking and no pending connections are present on the queue,

accept() returns an error as described below. The accept() function uses the

netconfig(4)

le to determine the STREAMS device le name associated with s. This is the device on which

the connect indication will be accepted. The accepted socket, ns, is used to read and write data

to and from the socket that connected to ns. It is not used to accept more connections. The

original socket (s) remains open for accepting further connections.

The argument addr is a result parameter that is lled in with the address of the connecting

entity as it is known to the communications layer. The exact format of the addr parameter is

determined by the domain in which the communication occurs.

The argument addrlen is a value-result parameter. Initially, it contains the amount of space

pointed to by addr; on return it contains the length in bytes of the address returned.

The accept() function is used with connection-based socket types, currently with

SOCK_STREAM.

It is possible to

select(3C) or poll(2) a socket for the purpose of an accept() by selecting or

polling it for a read. However, this will only indicate when a connect indication is pending; it is

still necessary to call accept().

The accept() function returns −1 on error. If it succeeds, it returns a non-negative integer

that is a descriptor for the accepted socket.

accept() will fail if:

EBADF The descriptor is invalid.

ECONNABORTED The remote side aborted the connection before the accept() operation

completed.

EFAULT The addr parameter or the addrlen parameter is invalid.

EINTR The accept() attempt was interrupted by the delivery of a signal.

EMFILE The per-process descriptor table is full.

Name

Synopsis

Description

Return Values

Errors

accept(3SOCKET)

man pages section 3: Networking Library Functions • Last Revised 24 Mar 201120

剩余869页未读，继续阅读

weixin_40191861_zj

粉丝: 83
资源: 1万+

Oracle Solaris 11网络库函数第3节：详细文档与指南

Oracle Solaris 11.1 man pages section3:Networking Library Functi

使用rust生成一段代码, 将 std::net::SocketAddr 转化为 windows_sys::Win32::Networking::WinSock::SOCKADDR_IN

apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example-ingress spec: rules: - host: example.com http: paths: - path: /foo pathType: Prefix backend: service: name: example-service port: name: http 增加number

restarting networking (via systemctl): networking.servicejob for networking.service failed because the control process exited with error code. see "systemctl status networking.service" and "journalctl -xe" for details.

[....] restarting networking (via systemctl): networking.servicejob for networking.service failed because the control process exited with error code. see "systemctl status networking.service" and "journalctl -xe" for details. failed!

Failed to restart networking.service: Unit networking.service not found

[....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details. failed!

Failed to restart networking.service: Unit networking.service not found.按照上述教程，报如上错误

Ubuntu22.04Failed to restart networking.service: Unit networking.service not found.

failed to restart networking.service:Unit networking.service not found

systemctl start networking Failed to start networking.service: Unit networking.service not found.

apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: nginx-ingress spec: ingressClassName: nginx rules: - host: www.lj.com http: paths: - path: / pathType: Prefix backend: service: name: nginx-service port: name: http 有问题，启动无法访问www.lj.com

Failed to restart networking.service: Unit networking.service not found.

Failed to start networking.service: Unit networking.service not found.

Failed to restart networking.service: Unit networking.service not found.怎么回事？

安装了networking.service后启动networking.service时Failed to start networking.service: Unit networking.service not found.

numexpr-2.8.3-cp38-cp38-win_amd64.whl

ujson-5.3.0-cp311-cp311-win_amd64.whl

最新资源