|
From: Joachim B. <jmb...@gm...> - 2002-05-31 04:12:22
|
Aidan Kehoe <ke...@pa...> writes: > Ar an 30=FA l=E1 de m=ED 5, scr=EDobh Frohwalt Egerer : > > > - I can't remember much more right now. When I'm on the phone with > > Joe he always gripes about not being able to delete open files in > > Windows. > > Programs written for win32 rely on this; it's not something that > should be taken out.=20 I do want "break" the programs in that case - the "normal" delete (command and syscall) should not do it, but 'del /fo locked_file' (or whatever) should do away with it. (This mostly pertains to 'misloaded' drivers and locked log files). It would require the underlying fs being able to hold open a file descriptor to an unnamed file, and free the file when closing the descriptor. Sorry, handle. As far as I know the Win2k kernel already can do this. Same thing for rename/move. Same thing for reading open files while they're written, something like 'tail' or 'less' should be possible no matter what the other app tells us we may do to the file. At least for the administrator. Extensive wishlist will follow... ;-) So long, Joe P.S.: Further up in the thread it was said that the administrator can gain 'kill services' rights through some setting - anyone knows from the top of their head which setting that is? Thanks! --=20 "I use emacs, which might be thought of as a thermonuclear word processor." -- Neal Stephenson, "In the beginning... was the command line" |