PT>> just another example of unixish dirty file system hacks, like doing
 PT>> unlink() on an open file :)

TS>You can debate about whether this is WAD or BUG. When 
TS>unlinking an open file it vanishes from all mounted 
TS>filesystems and only the internal subsystems have access to 
TS>the disk space via the stored inode number. This is quite 
TS>nice for security reasons when you don't want _anyone_ to 
TS>access the contents of the file.

   You can do the same thing under OS/2 by opening the file in deny
read/write mode.

TS>As soon as the last reference to the file is closed the 
TS>file is removed physically, i.e. the space is freed on the 
TS>volume.

   I believe that this is due to UNIX lacking effective file locking.  So
you can't stop a process from deleting a file while another process is
using it.  So you just allow the process with the open file to keep using
it - the deletion process will complete when there are no open handles to
the file.

    OS/2 doesn't allow a process/thread to delete a file when another
process/thread has it open...


  cya
___
 X MR/2 2.0 NR X This virus requires Microsoft Windows 3.x.

--- Maximus/2 2.02