Neither the UNIX root user nor the NT administrator can remove the files in question when the locks occur. I believe it is a side-effect of the Filer enforcing NT locks to UNIX clients. (I don't think Netapp is necessarily doing anything wrong here. I believe this is the correct behavior in most cases.) I very commonly encounter situations on NT systems where the administrator cannot remove a file that is open, no matter who owns it.
Of course, even if root *could* remove those files as root/administrator, I'd still like a way for the files owner to be able to remove them. I'd rather not have to give my build engineers root/administrator access to my filer.
----- Original Message ----- From: "Mike Sphar" mikey@Remedy.COM To: toasters@mathworks.com Sent: Friday, December 01, 2000 5:53 PM Subject: RE: Lock files
Neither the UNIX root user nor the NT administrator can remove the files
in
question when the locks occur. I believe it is a side-effect of the Filer enforcing NT locks to UNIX clients. (I don't think Netapp is necessarily doing anything wrong here. I believe this is the correct behavior in most cases.) I very commonly encounter situations on NT systems where the administrator cannot remove a file that is open, no matter who owns it.
But under NT, can the admin chown (take ownership) of a file that is locked, and then remove it? Also, can the admin remove a file that it itself has locked?
Of course, even if root *could* remove those files as root/administrator, I'd still like a way for the files owner to be able to remove them. I'd rather not have to give my build engineers root/administrator access to my filer.
I agree. I believe that UNIX and NT need to respect each-other's permissions, but it should not alter absolute power..
Bruce
-
Bruce Sterling Woodcock -
Mike Sphar