Speaking of that, I ran into some interesting behavior the other day. I'd had a recurrent problem where our build scripts couldn't delete a directory from the previous build because some windows user somewhere had left a window open on that share.

Well, I eventually discovered that by making the share read-only at the share level for everyone but our build engineers, that if I opened a window in that share, and then deleted it from UNIX, the delete would work and in fact my open window would automatically close.

However, we later found that the behavior was slightly different if the windows client was viewing the share through an Explorer window (i.e. using the double-paned File Explorer interface rather than just an open window.

Anyway, we found that when the share was accessed via Explorer, then when the rm command was executed from UNIX, the command would return successfully with no error, but the directory still remained. If I then closed the Explorer window, the directory would disappear. This was actually worse behavior from the build engineers perspective because at least before their scripts would get a permission denied error and exit, rather than continuing on assuming their work area was empty.

I suspect this is for the most part standard CIFS behavior, but it's still a little bizarre to see the rules applied differently depending on which tool was being used on the client.

Having said all that, yes I too would like an option whereby files or directories could be deleted no matter what their locking state was. This problem has been an unending source of complaints from our build engineers who ask questions like "Can we go back to the server where this wasn't a problem?" That server being an old Sparc running NFS and Samba. Obviously I don't want to go back to that old beast.

-----Original Message---- From: Bruce Sterling Woodcock [mailto:sirbruce@ix.netcom.com] Sent: Friday, May 25, 2001 4:25 AM To: Muhlestein, Mark; White, Lance; 'Chuck Ross'; Net App List (E-mail) Subject: Re: Why is root not root?

How about letting root delete files that are currently locked open on the NT-side like they can with NFS-locked files?

Bruce