cannot remove silly renamed files

cannot remove silly renamed files

[Topp, Kenneth]

[-- Attachment #1.1: Type: text/plain, Size: 467 bytes --]

Hi,

I've searched the archive but didn't find anything related.  2.6 doesn't
allow you to delete .nfsXXX (silly renamed) files from the host that has
it open.  2.4 and solaris 2.X has allowed one to shoot oneself in the
foot.

Can we update the code to do a rename twice then allow removal rather
then blocking it indefinitely?  The current code changes breaks expect
commands like "/bin/rm -rf dir/", which I'm sure is defined somewhere in
POSIX.

Ken

[-- Attachment #1.2: Type: text/html, Size: 1015 bytes --]

[-- Attachment #2: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: cannot remove silly renamed files

[Peter Staubach]

Topp, Kenneth wrote:
>
> Hi,
>
> I've searched the archive but didn't find anything related.  2.6 
> doesn't allow you to delete .nfsXXX (silly renamed) files from the 
> host that has it open.  2.4 and solaris 2.X has allowed one to shoot 
> oneself in the foot.
>
> Can we update the code to do a rename twice then allow removal rather 
> then blocking it indefinitely?  The current code changes breaks expect 
> commands like "/bin/rm -rf dir/", which I'm sure is defined somewhere 
> in POSIX.
>

Actually, I don't think that Solaris allows the .nfs temporary files to be
removed either.  The unlink(2) system call may not fail, but all that the
client does is to rename the file to a new .nfs temporary name.

Part of the danger of allowing these files to be really removed is, as you
say, to allow you to shoot yourself in the foot.  However, it would also
allow someone else to shoot you in the foot, which wouldn't be so good.

I might suggest rearchitecting the solution which depends upon things like
"rm -fr dir" to work by renaming "dir" to something else and then 
proceeding.

       ps

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs