Steve Dickson wrote:
On 08/17/2010 03:51 PM, Tom Haynes wrote:
Steve Dickson wrote:
In recent NFS v2/v3 to v4 transitions, one of the sticking points have been that fact v4 uses strings in the format
of "user@domain" instead of 32bit integers for uids and gids.
When the string can not be mapped, its mapped to the 'nobody'
user which is not optimal for things like backup servers and
such where the ids will not be know by both sides.
So this patch series enables the server to send out numeric string of uids and gids that do not have the '@domain' part.
The series also adds functionality to the client that parse these
type of strings and will use the numeric representation
of the ids iff the id exists on the client, which is sightly different that Solaris. Solaris dose not have that
"id must exist" restriction.
No, Solaris does have that restriction.
I thought so too.... but when I had an Open Solaris client
access an directory, on a Linux server, that was owned by a
user that was non-existent on either the server or client,
I got the numeric representation as the owner....
Basically:
osol# mount Linux-server:/home /mnt/home
osol# ls -ld /mnt/home/noid
drwxr-xr-x+ 2 111 111 4096 Aug 17 11:37 /mnt/home/noid/
osol# grep 111 /etc/passwd
osol#
steved.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
That is what I get for reading code instead of running it. :->
Actually, it might be that the server acts that way and not the client.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
