2 Dec
2000
2 Dec
'00
2:09 a.m.
Changing ownership of the file has not had any effect in my experience (this is on NT in general, not just Filers). The denying of access based on an open lock is completely separate from and takes precedence over any ownership as far as I've been able to determine.
And no, the Admin generally can't remove a file that has an open lock even if it opened the lock. Try deleting the executable for a process that is currently running and you will probably see what I mean.
--
Mike Sphar - Sr Systems Administrator - Engineering Support Services, BOFH,
GWP, MCP, MCP+I, MCSE, BFD
-----Original Message-----
From: Bruce Sterling Woodcock [mailto:sirbruce@ix.netcom.com]
Sent: Friday, December 01, 2000 6:06 PM
To: Mike Sphar; toasters@mathworks.com
Subject: Re: Lock files
----- 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