Killing other processes is not a healthy thing to do. If your scenario involves something like uninstallation, you could use the MoveFileEx API function to mark the file for deletion upon next reboot. If it appears that you really need to delete a file in use by another process, I’d recommend re-considering the actual problem … Read more
To lock the file: exec 3>filename # open a file handle; this part will always succeed flock -x 3 # lock the file handle; this part will block To release the lock: exec 3>&- # close the file handle You can also do it the way the flock man page describes: { flock -x 3 … Read more
If notepad can read the file then so can you, clearly the program didn’t put a read lock on the file. The problem you’re running into is that StreamReader will open the file with FileShare.Read. Which denies write access. That can’t work, the other program already gained write access. You’ll need to create the StreamReader … Read more
Alright, so I ended up going with the code I wrote here, on my website link is dead, view on archive.org (also available on GitHub). I can use it in the following fashion: from filelock import FileLock with FileLock(“myfile.txt”): # work with the file as it is now locked print(“Lock acquired.”)
Long ago it was impossible to reliably get the list of processes locking a file because Windows simply did not track that information. To support the Restart Manager API, that information is now tracked. I put together code that takes the path of a file and returns a List<Process> of all processes that are locking … Read more
Updated NOTE on this solution: Checking with FileAccess.ReadWrite will fail for Read-Only files so the solution has been modified to check with FileAccess.Read. ORIGINAL: I’ve used this code for the past several years, and I haven’t had any issues with it. Understand your hesitation about using exceptions, but you can’t avoid them all of the … Read more