On 04/07/98 09:49:22 you wrote:
Is this indeed proper bahavior? If so, is there a "Big Hammer" mode we can use to break locks if needed?
This doesn't directly answer your question but I did want to throw something out...
My view is that both root under UNIX and Administrator under NT should count as "Big Hammer". That is, these two should be able to override any and all locking behavior that would prevent an action.
However, I believe there are some things that even NT won't let the Administrator do, so I can see how for the purposes of emulation you would follow the same rules.
Under UNIX, though, root has always been able to do just about anything. The problem arises when an NT user has a file locked and in use and root on a UNIX box wants to delete that file. The answer is you can't do it. I think the same is true for modification as well.
To actually break the locks, you have to log into the filer and blow away that user's session. This just seems needlessly cumbersome. Assuming most environments have one with root access to the filesystem also having access to the filer, you are ultimately not "preventing" any behavior... you're just making it harder for the administrator. In other words, that UNIX rm should result in that CIFS user being logged out if need be.
Does anyone out there really desire to have an environment where even root can't blow such things away? If so, then perhaps this should be an option, but I would believe this group to be in the minority.
Bruce