Lines Matching full:server
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
182 (``man smb.conf``) on the Samba server system. Note that the cifs vfs,
187 supported this feature. Samba server does not allow symlinks that refer to files
193 would be forbidden. Samba 3.0.6 server or later includes the ability to create
194 such symlinks safely by converting unsafe symlinks (ie symlinks to server
195 files that are outside of the share) to a samba specific format on the server
196 that is ignored by local server applications and non-cifs clients and that will
197 not be traversed by the Samba server). This is opaque to the Linux client
201 applications running on the same server as Samba.
223 you do not trust the server to which are mounted, or if you do not have
226 running an altered binary on your local system (downloaded from a hostile server
231 for the server and sharename (which is somewhat similar to NFS style mount
232 syntax) instead of the more widely used UNC format (i.e. \\server\share)::
264 the Server's registry. Samba starting with version 3.10 will allow such
266 would be forbidden for Windows/CIFS semantics) as long as the server is
286 The ip address of the target server
288 The target server Universal Network Name (export) to
297 properly configured Samba server, the server provides
299 specified unless the server and clients uid and gid
300 numbering differ. If the server and client are in the
302 the server supports the Unix Extensions then the uid
303 and gid can be retrieved from the server (and uid
312 at the server, but there are cases in which an administrator
323 the server if possible. With this option, the value given in
324 the uid= option (on mount) will only be used if the server
330 cifs kernel driver which local user mounted. If the server
337 If CIFS Unix extensions are not supported by the server
342 heavily loaded server and/or network where reading from the
343 disk is faster than reading from the server (over the network).
345 number of calls to the server are reduced. However, local
351 If CIFS Unix extensions are not supported by the server
354 attempt to contact the server on this tcp port, before
359 names if the server supports it. If iocharset is
362 If server does not support Unicode, this parameter is
372 cifs protocol maximum) also requires that the server support
384 information from the server. This option allows to tune the
387 of calls to the server. Longer timeouts mean reduced number
388 of calls to the server at the expense of less stricter cache
393 server may still consider the share read-only)
448 target machine done by the server software.
453 client system. It is typically only needed when the server
455 client and server system do not match closely enough to allow
461 target machine done by the server software (of the server
464 Use server's inode numbers instead of generating automatically
468 note that the server does not guarantee that the inode numbers
469 are unique if multiple server side mounts are exported under a
477 This is now the default if server supports the
481 from the server). These inode numbers will vary after
483 but not all server filesystems support unique inode
486 If the CIFS Unix extensions are negotiated with the server
498 mkdir, mknod) which will result in the server setting the
499 uid and gid to the default (usually the server uid of the
500 user who mounted the share). Letting the server (rather than
520 to be sent to the server.
524 otherwise - read from the server. All written data are stored
526 it writes the data to the server.
532 Allow setfacl and getfacl to manage posix ACLs if server
539 attributes) to the server. This allows support of the
554 This has no effect if the server does not support
560 sensitive is the default if the server supports it).
576 and retrieving uids/gids/mode from the server) or to
577 work around a bug in server which implement the Unix
580 Do not send byte range lock requests to the server.
586 Even if the server supports posix (advisory) byte range
592 even if the cifs server would support posix advisory locks.
598 to the server (to force the server to write all dirty data
600 all dirty (cached) file data to the server and waits for the
601 server to respond to the write. Since SMB Flush can be
603 delaying slightly flushing the data to disk on the server),
605 applications that fsync too much, at a small risk of server
611 server claims to support it. This can help work around
612 a problem with parsing of DFS paths with Samba server
621 Specify the server 's netbios name (RFC1001 name) to use
622 when attempting to setup a session to the server.
625 support a default server name. A server name can be up
640 the server supports the CIFS Unix Extensions.
650 shares mounted to the same server are unaffected.
653 used by some applications such as Samba and NFSv4 server to
659 the file) for cases for example such as when the server does not
679 server requires signing also can be the default)
688 Retry file operations if server is not responding
809 server) SMB3 (or cifs) requests grouped by request type (read, write, close etc.).
810 Also recorded is the total bytes read and bytes written to the server for