Migrating from NFSv3 to v4 - NFSv4 ACL/permission confusion
Rick Macklem
rmacklem at uoguelph.ca
Mon Dec 6 22:59:14 UTC 2010
> Okay,
>
> Here is my dump command... The NFS host is 192.168.0.20:
>
> # tcpdump -s 0 -w dumpfile.txt host 192.168.0.20
> tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size
> 65535 bytes
>
This won't put anything on the screen. It's dumping to dumpfile.txt
(which is not a text file, but it doesn't matter what you call it).
If you email me dumpfile.txt as an attachment, that was what I was
referring to.
>
> In NFS mount:
>
> # ls -l
> total 2
> -rw-r--r-- 1 root wheel 0 Dec 4 23:19 blah
> -rw-r--r-- 1 root wheel 0 Dec 4 23:19 test2
> -rw-r--r-- 1 root wheel 0 Dec 4 23:19 test3
>
> # chown joe blah
>
> (no response)
>
> "joe" is indeed a local user on the NFS client side.
>
> This is not generating any tcpdump output though.
>
Do you mean that dumpfile.txt isn't growing while you do
this or just that there isn't anything being printed in
the window where tcpdump is running?
> # ls -l
> total 2
> -rw-r--r-- 1 root wheel 0 Dec 4 23:19 blah
> -rw-r--r-- 1 root wheel 0 Dec 4 23:19 test2
> -rw-r--r-- 1 root wheel 0 Dec 4 23:19 test3
>
> No actual permission change
>
You could try "chmod 600 blah" and see if that works? (It shouldn't
care about uid<->username mapping.)
>
> I created these files as root, so that much is being recognized...
>
Yep, which suggests that the uid<->username mapping is working.
rick
More information about the freebsd-fs
mailing list