On Tue, 28 Mar 2006, Han Boetes wrote:

> Otto Moerbeek wrote:
> > To demonstrate what I mean, here's an ugly diff, which makes the
> > access check of setattr TOSERVER behave like utimes(NULL). Han,
> > could you try this on your server? If it works, we at least know
> > a bit more what is going on.
>
> I applied your patch against the eh... second of march
> snapshot. Now I get this:
>
> ~% cat test
> #!/bin/sh
> echo foo > /mnt/nfs/nowplaying
> touch /mnt/nfs/nowplaying
> ~% l /mnt/nfs/nowplaying
> -rw-rw-r-- 1 han nfs 0 mrt 28 10:22 /mnt/nfs/nowplaying
> ~% sudo -u bascuppen ./test
> ./test[2]: cannot create /mnt/nfs/nowplaying: Operation not permitted

Hmmm.

> ~% # Now I chowned the file on the server.
> ~% l /mnt/nfs/nowplaying
> -rw-rw-r-- 1 bascuppen nfs 0 mrt 28 10:22 /mnt/nfs/nowplaying
> ~% ./test
> ./test[2]: cannot create /mnt/nfs/nowplaying: Operation not permitted

As which user was the command done?


I first though a truncate of a file was failing (if you look at the
log you'll see the setattr sz 0x0, but I made a litle test case that
just runs fine.

Also, it is strange your client report _creation_ failure. It should not
create a file in this case, AFAIK.

Can you modify your test script so it cleary reports if the redirect
is failing or the touch. Also, I like to know if you can edit the file
using an editor. Also, The permissions of the parent dir are
interesting. Please include ls -n info, and id info for your users; I
like to see the numbers.

Oh and please make sure you really ARE running the diff, I almost get
the feeling you're not...

-Otto