Lines Matching refs:cifs
38 3) select cifs from within the network filesystem choices
48 the modules directory e.g. /lib/modules/6.3.0-060300-generic/kernel/fs/smb/client/cifs.ko).
54 If you do not have the utility mount.cifs (in the Samba 4.x source tree and on
57 required, mount.cifs is recommended. Most distros include a ``cifs-utils``
62 domain to the proper network user. The mount.cifs mount helper can be
63 found at cifs-utils.git on git.samba.org
65 If cifs is built as a module, then the size and number of network buffers
69 modinfo <path to cifs.ko>
71 on kernel/fs/smb/client/cifs.ko the list of configuration changes that can be made
72 at module initialization time (by running insmod cifs.ko) can be seen.
92 with the cifs vfs. A way to enable such mounting is to mark the mount.cifs
93 utility as suid (e.g. ``chmod +s /sbin/mount.cifs``). To enable users to
96 1) mount.cifs version 1.4 or later
100 //server/usersharename /mnt/username cifs user 0 0
102 Note that when the mount.cifs utility is run suid (allowing user mounts),
110 mount.cifs with the following flag: CIFS_ALLOW_USR_SUID
112 There is a corresponding manual page for cifs mounting in the Samba 3.0 and
113 later source tree in docs/manpages/mount.cifs.8
119 the utility umount.cifs may be used. It may be invoked directly, or if
120 umount.cifs is placed in /sbin, umount can invoke the cifs umount helper
121 (at least for most versions of the umount utility) for umount of cifs
123 helper). As with mount.cifs, to enable user unmounts umount.cifs must be marked
124 as suid (e.g. ``chmod +s /sbin/umount.cifs``) or equivalent (some distributions
127 must be a cifs mount, and the uid of the current user must match the uid
131 (instead of using mount.cifs and unmount.cifs as suid) to add a line
161 cifs client, and that EA support is present in later versions of Samba (e.g.
170 then POSIX support in the CIFS configuration options when building the cifs
182 (``man smb.conf``) on the Samba server system. Note that the cifs vfs,
196 that is ignored by local server applications and non-cifs clients and that will
198 application using the cifs vfs. Absolute symlinks will work to Samba 3.0.5 or
207 (cifs.ko), you can use mount syntax like the following to access Samba or
210 mount -t cifs //9.53.216.11/e$ /mnt -o username=myname,password=mypassword
212 Before -o the option -v may be specified to make the mount.cifs
214 After -o the following commonly used cifs vfs specific options
221 Other cifs mount options are described below. Use of TCP names (in addition to
222 ip addresses) is available if the mount helper (mount.cifs) is installed. If
224 cifs signing enabled (and the physical network is insecure), consider use
230 not possible in mount.cifs yet, it is possible to use an alternate format
234 mount -t cifs tcp_name_of_server:share_name /mnt -o user=myname,pass=mypasswd
236 When using the mount helper mount.cifs, passwords may be specified via alternate
250 If no password is provided, mount.cifs will prompt for password entry
268 /proc/fs/cifs/LinuxExtensionsEnabled). In addition the mount option
308 who executed the mount (root, except when mount.cifs
330 cifs kernel driver which local user mounted. If the server
369 for cifs.ko. Setting CIFSMaxBufSize to a very large value
370 will cause cifs to use more memory and may reduce performance
372 cifs protocol maximum) also requires that the server support
383 After this timeout, the cifs client requests fresh attribute
412 when the cifs mount helper cifs.mount (version 1.1 or later)
434 Although ignored by the cifs kernel component, it is used by
435 the mount helper, mount.cifs. When mount.cifs is installed it
438 the cifs vfs.
440 Although ignored by the kernel component, the mount.cifs
475 this mount option will have no effect. Exporting cifs mounts
476 under nfsd requires this mount option on the cifs mount.
582 with cifs style mandatory byte range locks (and most
583 cifs servers do not yet support requesting advisory
591 forcing the cifs client to only send mandatory locks
592 even if the cifs server would support posix advisory locks.
597 fsync call then the cifs client does not send an SMB Flush
599 for this file immediately to disk), although cifs still sends
606 crash. If this mount option is not set, by default cifs will
657 is not oplocked, it could still be cacheable (ie cifs client
662 will allow the cifs client to check for leases (only) locally
678 /proc/fs/cifs/PacketSigningEnabled on or if
693 The mount.cifs mount helper also accepts a few mount options before -o
699 -V print mount.cifs version
703 With most 2.6 kernel versions of modutils, the version of the cifs kernel
706 Misc /proc/fs/cifs Flags and Debug Info
713 shares, features enabled as well as the cifs.ko
753 cifs kernel unless CONFIG_CIFS_DEBUG2 is enabled in the
758 | log cifs informational messages | 0x01 |
760 | log return codes from cifs entry points | 0x02 |
789 /proc/fs/cifs (after the cifs module has been installed or built into the
790 kernel, e.g. insmod cifs). To enable a feature set it to 1 e.g. to enable
793 echo 7 > /proc/fs/cifs/cifsFYI
803 echo 1 > /proc/fs/cifs/traceSMB
805 Per share (per client mount) statistics are available in /proc/fs/cifs/Stats.
809 server) SMB3 (or cifs) requests grouped by request type (read, write, close etc.).
813 Statistics can be reset to zero by ``echo 0 > /proc/fs/cifs/Stats`` which may be
816 Also note that ``cat /proc/fs/cifs/DebugData`` will display information about
820 of the helper program cifs.upcall to be present and to be configured in the
821 /etc/request-key.conf file. The cifs.upcall helper program is from the Samba
824 cifs.upcall helper program), instead of using Kerberos, is sufficient for
830 a user space helper (such as cifs.upcall) to be present in order to
836 To use cifs Kerberos and DFS support, the Linux keyutils package should be
840 create cifs.spnego * * /usr/local/sbin/cifs.upcall %k
841 create dns_resolver * * /usr/local/sbin/cifs.upcall %k
848 /sys/module/cifs/parameters/<param>
852 echo "value" > /sys/module/cifs/parameters/<param>
857 modinfo cifs (or modinfo smb3)