----- Original Message ----- From: Bond, Andrew abond@netapp.com To: bhaskar.g@philips.com; toasters@mathworks.com Sent: Wednesday, March 08, 2000 3:42 AM Subject: RE: Problem in ownerships
I'd take a quess that the file is on a qtree (or volume) with NTFS
security.
This is expected behaviour in that situation.
Good point. I would have expected a different error message (EACCES rather than EPERM), but it appears that chown(2) and utimes(2) may interpret those very strictly, and assume that EPERM must mean that you are not the owner if you're not root, rather than simply being denied write access. They don't seem to consider the possibility of being denied write access even when the times argument is non-NULL.
Still, wouldn't it be more appropriate for the filer to return NFS[3]ERR_ACCES instead of NFS[3]ERR_PERM in those situations?
Bruce