Searched full:server (Results 1 – 25 of 174) sorted by relevance
1234567
/Documentation/ABI/testing/ |
D | sysfs-class-rnbd-server | 1 What: /sys/class/rnbd-server 5 Description: provide information about RNBD-server. 7 What: /sys/class/rnbd-server/ctl/ 12 block device is created under /sys/class/rnbd-server/ctl/devices/. 14 What: /sys/class/rnbd-server/ctl/devices/<device_name>/block_dev 23 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/ 30 /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/ 34 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/read_only 40 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/mapping_path 46 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/access_mode
|
D | sysfs-class-rtrs-server | 1 What: /sys/class/rtrs-server 8 What: /sys/class/rtrs-server/<session-name>/paths/ 14 on server. 16 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/disconnect 23 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_name 29 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_port 35 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/src_addr 41 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/dst_addr 47 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/stats/rdma
|
D | sysfs-class-rnbd-client | 33 a given session on the client and on the server. 37 describes a connection between the client and the server by 50 The connection will be established to this server from any client IP address. 63 Path to the block device on the server side. Path is specified 64 relative to the directory on server side configured in the 74 have different devices namespace, e.g. server was configured with 76 client has this string "sessname=blya device_path=sda", then server 81 mapped as "ro" read-only or "rw" read-write. The server allows 92 be found on the server, it will fail with ENOENT.
|
D | sysfs-block-rnbd | 21 returns "open" when the device is successfully mapped from the server 22 and accepting I/O requests. When the connection to the server gets 31 server. The entry "session" contains the name of the session, that 33 was passed as server parameter to the map_device entry.
|
/Documentation/admin-guide/cifs/ |
D | usage.rst | 66 and maximum number of simultaneous requests to one server can be configured. 100 //server/usersharename /mnt/username cifs user 0 0 132 to the file /etc/fstab for each //server/share you wish to mount, but 142 (CIFS/SMB1), we recommend using a server that supports the SNIA CIFS 146 not have a server that supports the Unix extensions for CIFS (such as Samba 147 2.2.5 or later). To enable the Unix CIFS Extensions in the Samba server, add 152 to your smb.conf file on the server. Note that the following smb.conf settings 153 are also useful (on the Samba server) when the majority of clients are Unix or 160 Note that server ea support is required for supporting xattrs from the Linux 178 enabled on the server and client, subsequent setattr calls (e.g. chmod) can [all …]
|
D | todo.rst | 19 currently the only two server side copy mechanisms supported) 32 roundtrips to the server and improve performance. Various cases 52 j) Create UID mapping facility so server UIDs can be mapped on a per 53 mount or a per server basis to client UIDs or nobody if no mapping 74 move, server failover, and server adapter changes. And also improve other 76 different servers, and the server we are connected to has gone down. 113 1) check out max path names and max path name components against various server
|
D | introduction.rst | 7 protocol which was the successor to the Server Message Block 16 Server), as well as by Samba (which provides excellent 17 CIFS/SMB2/SMB3 server support and tools for Linux and many other 30 improvements. Since both Samba server and this filesystem client support
|
/Documentation/admin-guide/nfs/ |
D | nfs-rdma.rst | 15 and server software. 17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server 46 The first kernel release to contain both the NFS/RDMA client and server was 102 nfs-utils on the server. Furthermore, only the mount.nfs command from 107 The NFS/RDMA client and server are both included in the mainline Linux 125 - Configure the NFS client and server 128 NFS server support enabled. These and other NFS related configuration 134 are turned on. The NFS/RDMA client and server are configured via the hidden 139 and server will not be built 142 in this case the NFS/RDMA client and server will be built as modules [all …]
|
D | pnfs-scsi-server.rst | 3 pNFS SCSI layout server user guide 6 This document describes support for pNFS SCSI layouts in the Linux NFS server. 7 With pNFS SCSI layouts, the NFS server acts as Metadata Server (MDS) for pNFS, 12 To use pNFS SCSI layouts with the Linux NFS server, the exported file 19 On a server built with CONFIG_NFSD_SCSI, the pNFS SCSI volume support is
|
D | pnfs-block-server.rst | 2 pNFS block layout server user guide 5 The Linux NFS server now supports the pNFS block layout extension. In this 6 case the NFS server acts as Metadata Server (MDS) for pNFS, which in addition 11 To use pNFS block layouts with the Linux NFS server the exported file 18 On the server, pNFS block volume support is automatically if the file system 23 If the nfsd server needs to fence a non-responding client it calls
|
D | nfsroot.rst | 18 In order to use a diskless system, such as an X-terminal or printer server for 24 of this text 'client' means the diskless system, and 'server' means the NFS 25 server. 49 both the server and the name of the directory on the server to mount as root. 59 nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>] 63 <server-ip> Specifies the IP address of the NFS server. 68 <root-dir> Name of the directory on the server to mount as root. 76 port = as given by server portmap daemon 88 ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<nt… 109 <server-ip> IP address of the NFS server. [all …]
|
D | index.rst | 13 pnfs-block-server 14 pnfs-scsi-server
|
D | nfsd-admin-interfaces.rst | 11 The server is always started by the first write of a nonzero value to 38 Note that the rpc server requires the caller to serialize addition and 39 removal of listening sockets, and startup and shutdown of the server.
|
/Documentation/powerpc/ |
D | hvcs.rst | 2 HVCS IBM "Hypervisor Virtual Console Server" Installation Guide 36 This is the device driver for the IBM Hypervisor Virtual Console Server, 55 major and minor numbers are associated with each vty-server. Directions 79 <*> IBM Hypervisor Virtual Console Server Support 91 <M> IBM Hypervisor Virtual Console Server Support 114 We think that 1024 is currently a decent maximum number of server adapters 206 is a vty-server device configured for that node. 249 Hotplug add and remove of vty-server adapters affects which /dev/hvcs* node 250 is used to connect to each vty-server adapter. In order to determine which 251 vty-server adapter is associated with which /dev/hvcs* node a special sysfs [all …]
|
/Documentation/admin-guide/blockdev/ |
D | nbd.rst | 9 can use a remote server as one of its block devices. So every time 11 request over TCP to the server, which will reply with the data read. 16 For more information, or to download the nbd-client and nbd-server 20 system, as the nbd-server is completely in userspace. In fact, 21 the nbd-server has been successfully ported to other operating
|
/Documentation/networking/ |
D | snmp_counter.rst | 1036 Run the ping command against the public dns server 8.8.8.8:: 1063 The Linux server sent an ICMP Echo packet, so IpOutRequests, 1065 server got ICMP Echo Reply from 8.8.8.8, so IpInReceives, IcmpInMsgs, 1080 On server side, we run:: 1090 The server listened on tcp 9000 port, the client connected to it, they 1093 On server side, we can find below nstat output:: 1108 When the server received the first SYN, it replied a SYN+ACK, and came into 1109 SYN-RCVD state, so TcpPassiveOpens increased 1. The server received 1110 SYN, sent SYN+ACK, received ACK, so server sent 1 packet, received 2 1122 Run nc on server:: [all …]
|
D | rxrpc.rst | 28 (#) Example server usage. 61 receives a blob (the reply), and the server receives the request and then 68 manage security on the client end. The server end must of necessity be 107 shared between client and server connections (connections have a 139 requested, the server then issues a "challenge" and then the client 142 upon it use that same security. In the event that the server lets a 160 reached the server. 175 make multiple simultaneous calls to the same service. One server socket 194 (#) A server-side connection is shared if the client says it is. 208 (#) A socket is made into a server socket by binding an address with a [all …]
|
D | ipvs-sysctl.rst | 29 If set, disable the director function while the server is 39 connection will be delivered to the same real server that was 74 directly when no cache server is available and destination 137 packets when its destination server is not available. It may 139 destination server (because of server overload or wrong 140 detection) and add back the server later, and the connections 141 to the server can continue. 145 destination server is not available, then the client program 155 persistent templates when the destination server is quiescent. 156 This may be useful, when a user makes a destination server [all …]
|
/Documentation/filesystems/cifs/ |
D | cifsroot.rst | 23 which is only supported by the Samba server. SMB1 is the older 35 Server configuration 42 server min protocol = NT1 57 cifsroot=//<server-ip>/<share>[,options] 60 located in the <server-ip> and <share> specified in this option. 64 server-ip 65 IPv4 address of the server.
|
/Documentation/ABI/stable/ |
D | sysfs-acpi-pmprofile | 21 4 Enterprise Server 22 5 SOHO Server 24 7 Performance Server
|
/Documentation/devicetree/bindings/net/ |
D | marvell,prestera.txt | 13 - dfx: phandle reference to the "DFX Server" node 31 DFX Server bindings 35 - compatible: must be "marvell,dfx-server", "simple-bus" 41 dfx-server { 42 compatible = "marvell,dfx-server", "simple-bus";
|
/Documentation/filesystems/ |
D | 9p.rst | 39 For remote file server:: 47 For server running on QEMU host with virtio transport:: 51 where mount_tag is the tag associated by the server to each of the exported 73 uname=name user name to attempt mount as on the remote server. The 74 server may override or ignore this value. Certain user 77 aname=name aname specifies the file tree to access when the server is 118 port=n port to connect to on the remote server 168 as the server returns some data instead of trying to fill the read 177 9p client and server implementations are listed on 180 A 9p2000.L server is being developed by LLNL and can be found
|
D | orangefs.rst | 44 Running ORANGEFS On a Single Server 51 On Fedora, install orangefs and orangefs-server:: 53 dnf -y install orangefs orangefs-server 55 There is an example server configuration file in 68 pvfs2-server -f /etc/orangefs/orangefs.conf 70 Start the server:: 72 systemctl start orangefs-server 74 Test the server:: 96 Building ORANGEFS on a Single Server 117 should use your server's hostname, rather than "localhost" when [all …]
|
/Documentation/filesystems/nfs/ |
D | index.rst | 11 rpc-server-gss 12 nfs41-server
|
D | rpc-server-gss.rst | 7 server and the NFS client's NFSv4.0 callback server. (But note that 8 NFSv4.1 and higher don't require the client to act as a server for the 46 NFS Server Legacy Upcall Mechanism 67 NFS Server New RPC Upcall Mechanism
|
1234567