Lines Matching refs:server
76 and maximum number of simultaneous requests to one server can be configured.
91 //server/usersharename /mnt/username cifs user 0 0
124 to the file /etc/fstab for each //server/share you wish to mount, but
130 To get the maximum benefit from the CIFS VFS, we recommend using a server that
134 not have a server that supports the Unix extensions for CIFS (such as Samba
135 2.2.5 or later). To enable the Unix CIFS Extensions in the Samba server, add
140 to your smb.conf file on the server. Note that the following smb.conf settings
141 are also useful (on the Samba server) when the majority of clients are Unix or
148 Note that server ea support is required for supporting xattrs from the Linux
166 enabled on the server and client, subsequent setattr calls (e.g. chmod) can
170 ("man smb.conf") on the Samba server system. Note that the cifs vfs,
175 supported this feature. Samba server does not allow symlinks that refer to files
179 would be forbidden. Samba 3.0.6 server or later includes the ability to create
180 such symlinks safely by converting unsafe symlinks (ie symlinks to server
181 files that are outside of the share) to a samba specific format on the server
182 that is ignored by local server applications and non-cifs clients and that will
183 not be traversed by the Samba server). This is opaque to the Linux client
187 applications running on the same server as Samba.
208 you do not trust the server to which are mounted, or if you do not have
211 running an altered binary on your local system (downloaded from a hostile server
216 for the server and sharename (which is somewhat similar to NFS style mount
217 syntax) instead of the more widely used UNC format (i.e. \\server\share):
247 would be forbidden for Windows/CIFS semantics) as long as the server is
260 ip The ip address of the target server
261 unc The target server Universal Network Name (export) to
268 properly configured Samba server, the server provides
270 specified unless the server and clients uid and gid
271 numbering differ. If the server and client are in the
273 the server supports the Unix Extensions then the uid
274 and gid can be retrieved from the server (and uid
283 at the server, but there are cases in which an administrator
292 the server if possible. With this option, the value given in
293 the uid= option (on mount) will only be used if the server
297 cifs kernel driver which local user mounted. If the server
302 file_mode If CIFS Unix extensions are not supported by the server
306 heavily loaded server and/or network where reading from the
307 disk is faster than reading from the server (over the network).
309 number of calls to the server are reduced. However, local
314 dir_mode If CIFS Unix extensions are not supported by the server
316 port attempt to contact the server on this tcp port, before
320 names if the server supports it. If iocharset is
323 If server does not support Unicode, this parameter is
332 cifs protocol maximum) also requires that the server support
342 information from the server. This option allows to tune the
345 of calls to the server. Longer timeouts mean reduced number
346 of calls to the server at the expense of less stricter cache
350 server may still consider the share read-only)
389 target machine done by the server software.
393 client system. It is typically only needed when the server
395 client and server system do not match closely enough to allow
401 target machine done by the server software (of the server
403 serverino Use server's inode numbers instead of generating automatically
407 note that the server does not guarantee that the inode numbers
408 are unique if multiple server side mounts are exported under a
416 This is now the default if server supports the
419 from the server). These inode numbers will vary after
421 but not all server filesystems support unique inode
423 setuids If the CIFS Unix extensions are negotiated with the server
434 mkdir, mknod) which will result in the server setting the
435 uid and gid to the default (usually the server uid of the
436 user who mounted the share). Letting the server (rather than
454 to be sent to the server.
457 otherwise - read from the server. All written data are stored
459 it writes the data to the server.
463 acl Allow setfacl and getfacl to manage posix ACLs if server
468 attributes) to the server. This allows support of the
479 This has no effect if the server does not support
483 sensitive is the default if the server supports it).
496 and retrieving uids/gids/mode from the server) or to
497 work around a bug in server which implement the Unix
499 nobrl Do not send byte range lock requests to the server.
504 forcemandatorylock Even if the server supports posix (advisory) byte range
510 even if the cifs server would support posix advisory locks.
515 to the server (to force the server to write all dirty data
517 all dirty (cached) file data to the server and waits for the
518 server to respond to the write. Since SMB Flush can be
520 delaying slightly flushing the data to disk on the server),
522 applications that fsync too much, at a small risk of server
527 server claims to support it. This can help work around
528 a problem with parsing of DFS paths with Samba server
534 servern Specify the server 's netbios name (RFC1001 name) to use
535 when attempting to setup a session to the server.
538 support a default server name. A server name can be up
551 the server supports the CIFS Unix Extensions.
559 shares mounted to the same server are unaffected.
561 used by some applications such as Samba and NFSv4 server to
567 the file) for cases for example such as when the server does not
580 server requires signing also can be the default)
585 hard Retry file operations if server is not responding
612 and will be used if the server requires
614 required even if the server considers packet
707 represent the number of successful (ie non-zero return code from the server)
709 Also recorded is the total bytes read and bytes written to the server for
713 that they represent all for that share, not just those for which the server