Lines Matching refs:uid

119 must be a cifs mount, and the uid of the current user must match the uid
133 Note that uid, gid and file permissions will display default values if you do 
265   uid		Set the default uid for inodes. For mounts to servers
268 		the uid, gid and mode so this parameter should  not be
269 		specified unless the server and clients uid and gid
272 		the server supports the Unix Extensions then the uid
273 		and gid can be retrieved from the server (and uid
276 		extensions, the default uid (and gid) returned on lookup
277 		of existing files will be the uid (gid) of the person
279 		is configured setuid for user mounts) unless the "uid=" 
280 		(gid) mount option is specified.  For the uid (gid) of newly
282 		the last mount of the server share, the expected uid 
288 		servers which do not report a uid/gid owner
293 		at version 1.10 or higher to support specifying the uid
361   perm          Client does permission checks (vfs_permission check of uid
394 		the client will attempt to set the effective uid and gid of
398 		instead of using the default uid and gid specified on
399 		the mount, cache the new file's uid and gid locally which means
400 		that the uid for the file can change when the inode is
402   nosetuids     The client will not attempt to set the uid and gid on
405 		uid and gid to the default (usually the server uid of the
407 		the client) set the uid and gid is the default. If the CIFS
408 		Unix Extensions are not negotiated then the uid and gid for
409 		new files will appear to be the uid (gid) of the mounter or the
410 		uid (gid) parameter specified on the mount.
556 			if more than one uid accesses the same mount
631 			support and want to map the uid and gid fields