[DGD]File system bug

[Felix A. Croes]

On Mon, 6 Sep 1999, Jason Cone wrote:

> This report is a bit more signifcant than the earlier syntactical nitpick. :)
> As a disclaimer, the OS that this is encountered on is Windows 2000 Professional
> Build 2099, so it could be easily argued that DGD shouldn't be supported on it
> thereby negating any of this. ;)  But because Win2K is my primary development
> platform and because I haven't encountered behavior like this before, I'm
> inclinded to think that DGD and Win2K aren't getting along.  As statement of
> fact, I could not recreate this on Linux.
> 
> Anyway, if I create a directory (within the MUD using commands or
> programmatically using the make_dir() kfun) and then remove it (again, within
> the MUD using commands or programmatically using the remove_dir() kfun), life is
> good.  Alternatively, after creating said directory, I create a file within that
> directory and then delete it (all from with the MUD, using ed() and
> remove_file()).  I then to proceed to attempt to remove the directory that
> contained the file and life is suddenly bad.  remove_dir() returns 0 which I can
> only assume that a file handle is still being referenced somewhere by something.

I see no file descriptor/handle leaks in relevant places.  If memory of
Windows file system semantics serves me correctly, it is impossible to
remove a file that has just been created and is still open for writing.
Also, the file should show up with length 0 in a directory listing until
the descriptor has been closed.

If Windows 2000 has some new file recovery thingy, now is the time to turn
that off.  In the meantime,

What version of DGD?
What filesystem type, DOS or NTFS?
Can you remove the directory after you fully quit and restart DGD?

Regards,
Dworkin


List config page:  http://list.imaginary.com/mailman/listinfo/dgd