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   forceuid	Set the default uid for inodes to the uid
269 		the uid, gid and mode so this parameter should not be
270 		specified unless the server and clients uid and gid
273 		the server supports the Unix Extensions then the uid
274 		and gid can be retrieved from the server (and uid
277 		extensions, the default uid (and gid) returned on lookup
278 		of existing files will be the uid (gid) of the person
280 		is configured setuid for user mounts) unless the "uid=" 
285 		servers which do not report a uid/gid owner
290   forcegid	(similar to above but for the groupid instead of uid) (default)
291   noforceuid	Fill in file owner information (uid) by requesting it from
293 		the uid= option (on mount) will only be used if the server
295   noforcegid	(similar to above but for the group owner, gid, instead of uid)
296   uid		Set the default uid for inodes, and indicate to the
298 		supports the unix extensions the default uid is
386   perm          Client does permission checks (vfs_permission check of uid
424 		the client will attempt to set the effective uid and gid of
428 		instead of using the default uid and gid specified on
429 		the mount, cache the new file's uid and gid locally which means
430 		that the uid for the file can change when the inode is
432   nosetuids     The client will not attempt to set the uid and gid on
435 		uid and gid to the default (usually the server uid of the
437 		the client) set the uid and gid is the default. If the CIFS
438 		Unix Extensions are not negotiated then the uid and gid for
439 		new files will appear to be the uid (gid) of the mounter or the
440 		uid (gid) parameter specified on the mount.
613 			if more than one uid accesses the same mount
688 			support and want to map the uid and gid fields